M
Mark Tangard
One of my global VBA add-ins is causing a problem I've seen once before, but the
remedy that worked then isn't solving the problem.
With this add-in loaded and Word closed, double-clicking a Word file from a
normal folder window opens Word, but does not open the file. No error message
appears; but the Word window's title bar goes dim after a half-second or so,
indicating it's inactive. Often (but not always) a second instance of Word
(also empty) is also opened.
If Word is already open, double-clicking a Word file from a normal folder window
proceeds as usual.
Removing all my other add-ins and adding them back in one-by-one shows this one
is definitely the culprit. (Regenerating a fresh Normal.dot also has no
effect.) This happened once before, with a different add-in, and simply
rebuilding it manually stopped the behavior. (Running the Code Cleaner didn't
fix it, although by 'rebuilding' above I mean doing essentially the same thing
the Cleaner does, just mostly by manual cut-and-paste.) The same fix this time
has no result. (One difference: Last time was in Word 2000; we're now in Word
2003.)
This add-in isn't especially huge (700K) and does only pretty basic stuff,
nothing too complex, has no extra references other than the VBA Extensibility
library, doesn't automate other apps, etc. I run a handful of other add-ins
with similar content with no ill effect. The only major difference is that this
one gets edited more often than the others.
Any suggestions appreciated.
remedy that worked then isn't solving the problem.
With this add-in loaded and Word closed, double-clicking a Word file from a
normal folder window opens Word, but does not open the file. No error message
appears; but the Word window's title bar goes dim after a half-second or so,
indicating it's inactive. Often (but not always) a second instance of Word
(also empty) is also opened.
If Word is already open, double-clicking a Word file from a normal folder window
proceeds as usual.
Removing all my other add-ins and adding them back in one-by-one shows this one
is definitely the culprit. (Regenerating a fresh Normal.dot also has no
effect.) This happened once before, with a different add-in, and simply
rebuilding it manually stopped the behavior. (Running the Code Cleaner didn't
fix it, although by 'rebuilding' above I mean doing essentially the same thing
the Cleaner does, just mostly by manual cut-and-paste.) The same fix this time
has no result. (One difference: Last time was in Word 2000; we're now in Word
2003.)
This add-in isn't especially huge (700K) and does only pretty basic stuff,
nothing too complex, has no extra references other than the VBA Extensibility
library, doesn't automate other apps, etc. I run a handful of other add-ins
with similar content with no ill effect. The only major difference is that this
one gets edited more often than the others.
Any suggestions appreciated.