(I posted this to the wrong group before - I hope this is the correct one.)
I have several global templates in Startup (Word 2003). Some of which
reference a COM DLL to show various dialogs and perform tasks while I'm
working in Word. The DLL as well as the .dot files are properly code-signed
and security settings all seem to be in order.
Most of the macros in the global .dot work fine. However, at some point
after one of my macros runs, part of the Word UI suddenly becomes "frozen"
in the sense that the scroll bars no longer respond to my mouse clicks, etc.
I can click on the toolbar buttons and type into the document, but I can't
scroll the document window at all with the mouse.
Additionally, when I look at the Tools, Templates and Add-ins dialog box, it
has emptied out completely (I know my global templates are loaded because I
can still see their toolbars but they are no longer listed). And the
Organizer button is disabled, as are the Add and Remove buttons.
There has to be a reasonable explanation for this - has my macro somehow
offended Office security? It's only automating Word objects - it contains
no commands that try to access the VBA IDE or Outlook so I don't think that
it would be mistaken for a virus.
Also, I have double-checked that Application.ScreenUpdating = True, and am
not using the ScreenRefresh statement (which I initially thought might be
the cause).
I can't find anything about this on the KB or Google, and I am pretty sure
this is no virus. Please help!
Thanks!
Karen
Word Heretic - 23 May 2005 02:08 GMT
G'day "Karen Walker" <terryandkaren@centurytel.net>,
I am guessing something has done a
Application.ScreenUpdating = False
without its corresponding
Application.ScreenUpdating = True
Perhaps this is being triggered by a badly-handled error when it runs.
Steve Hudson - Word Heretic
steve from wordheretic.com (Email replies require payment)
Without prejudice
Karen Walker reckoned:
>(I posted this to the wrong group before - I hope this is the correct one.)
>
[quoted text clipped - 28 lines]
>Thanks!
>Karen
Karen Walker - 23 May 2005 18:08 GMT
Thanks Steve. I verified that it was not being caused by ScreenUpdating =
False and ScreenRefresh.
It seems a more insidious, mysterious force is at work here :)
Karen
> G'day "Karen Walker" <terryandkaren@centurytel.net>,
>
[quoted text clipped - 9 lines]
>
> Steve Hudson - Word Heretic
Word Heretic - 26 May 2005 02:31 GMT
G'day "Karen Walker" <terryandkaren@centurytel.net>,
Starting to play in the cracks here - what about ensuring each project
has a unique name. Eg Template A, rename its default VBA project name
to TemplateA.
Steve Hudson - Word Heretic
steve from wordheretic.com (Email replies require payment)
Without prejudice
Karen Walker reckoned:
>Thanks Steve. I verified that it was not being caused by ScreenUpdating =
>False and ScreenRefresh.
[quoted text clipped - 16 lines]
>>
>> Steve Hudson - Word Heretic