E
Ed
I sure hope someone can shed some light on this! One and only one user in
our office has a problem running macros. Supposedly, all our computers had
the same image at set up, with the same OS (Win XP) and the same version of
Office (2002) with the same DLLs. I am the designated "macro guru" (which
only means I know Alt+F11 and I'm not afraid to play there!), so I get
called over for any problems. Any of the rest of us can run a macro with no
problems (other than my coding errors).
She runs the same macro and gets "Code execution has been interrupted"
several times. Hit "Debug" and F5 and the macro continues until it stops
again. Never an error - just "interrupted". And the macro stops on things
like: "End If", "Loop Until ", and so forth. This last time, the macro was
trying to process about 1500 files, and stopped 4 or 5 times on each file!
Where do I start to look for the problem? Memory? An options setting?
Something else?
Ed
our office has a problem running macros. Supposedly, all our computers had
the same image at set up, with the same OS (Win XP) and the same version of
Office (2002) with the same DLLs. I am the designated "macro guru" (which
only means I know Alt+F11 and I'm not afraid to play there!), so I get
called over for any problems. Any of the rest of us can run a macro with no
problems (other than my coding errors).
She runs the same macro and gets "Code execution has been interrupted"
several times. Hit "Debug" and F5 and the macro continues until it stops
again. Never an error - just "interrupted". And the macro stops on things
like: "End If", "Loop Until ", and so forth. This last time, the macro was
trying to process about 1500 files, and stopped 4 or 5 times on each file!
Where do I start to look for the problem? Memory? An options setting?
Something else?
Ed