K
Karen Walker
(I posted this to the wrong group before - I hope this is the correct one.)
I have a global templates in Word 2003 (in the Startup folder),
which references a COM DLL to show various dialogs and perform tasks while
I'm
working in Word. The DLL as well as the .dot file is properly code-signed.
(Note: this particular machine is set to Low security, and nothing is listed
under Trusted Publishers.)
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.
However, I can still click on the toolbar buttons and type into the
document.
Additionally, the Tools, Templates and Add-ins dialog box, has
completely emptied out, and the Organizer, Add and Remove buttons
are disabled. I know my global template is still loaded because I
can still see its toolbars, but it is no longer listed in Templates &
Add-ins.
PS, 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
I have a global templates in Word 2003 (in the Startup folder),
which references a COM DLL to show various dialogs and perform tasks while
I'm
working in Word. The DLL as well as the .dot file is properly code-signed.
(Note: this particular machine is set to Low security, and nothing is listed
under Trusted Publishers.)
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.
However, I can still click on the toolbar buttons and type into the
document.
Additionally, the Tools, Templates and Add-ins dialog box, has
completely emptied out, and the Organizer, Add and Remove buttons
are disabled. I know my global template is still loaded because I
can still see its toolbars, but it is no longer listed in Templates &
Add-ins.
PS, 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