VB debugger "pop up" problem

[Dan Kelly]

We have a small macro embedded in our Normal template that is called whenever
someone uses the correct shortcut to Word (as below):

"C:\Program Files\Microsoft Office\Office\WINWORD.EXE" /n /mNewDoc

All the Macro does is call a program on a Network drive, which then allows
the user to select information from the company database to insert into
various document templates.

On one user something weird is happening - the VB debugger is appearing and
stopping at the call to the Network program. There is no breakpoint defined
in the VB, and the Network drive exists and runs if you press F8, etc

It's, as you can imagine, rather annoying.

Anyone seen similar?

 

[Jezebel]

I've seen this problem -- VBA stopping at an arbitrary line, as if it were a
breakpoint. In each case it seemed to be a corruption of the code module:
copy the code to a new module and deleting the old seemed to fix it. Beyond
that, no idea what causes it.

 

[Rob]

If that doesn't fix the problem you can also check that the user in question
has rights to access any part of this that is on a network drive (modules,
templates, external programs, etc). Also check all the references on the
user's machine. Something might be missing (a module, a dll, etc). It will
say in all caps MISSING if it is.

 

[Dan Kelly]

Do you mean within the macro?

As there's only one line within the Macro of the template I'll switch it for
a fresh copy from the Network and see what that does.