Ed
Mon Oct 02 17:07:39 CDT 2006
Thanks for the help, Jonathan. I appreciate it.
Ed
"Jonathan West" <jwest@mvps.org> wrote in message
news:eL72blm5GHA.4304@TK2MSFTNGP03.phx.gbl...
>
> "Ed" <ed_millis@NO_SPAM.yahoo.com> wrote in message
> news:ursNjYl5GHA.3452@TK2MSFTNGP05.phx.gbl...
>>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?
>>
>
> First of all, open the VBA editor on the offending machine, and go to
> Tools, Options. Click the General tab, and in the "Error handling" area,
> and make sure that the option is set to "Break on unhandled errors"
>
> If that doesn't fix it, copy a new set of templates across, just in case
> this particular copy have been corrupted.
>
> If that doesn't fix it, and if you have been editing the VBA in these
> templates a lot, then try the measures described in this article
>
> Combatting Template Bloat
>
http://www.word.mvps.org/FAQs/MacrosVBA/TemplateBloat.htm
>
> If necessary, then try deleting the user's copy of normal.dot and see if
> things start to behave
>
> If there is still a problem, go to the Help menu in Word and to a "Detect
> & Repair".
>
> If that doesn't fix it, then reinstalling from the image might be the only
> solution.
>
>
> --
> Regards
> Jonathan West - Word MVP
> www.intelligentdocuments.co.uk
> Please reply to the newsgroup
> Keep your VBA code safe, sign the ClassicVB petition www.classicvb.org
>