Hello all,

I've got some VBA code in an Excel 2003 file that opens up other Excel
files, updates links, runs some macros, and generates a new Excel file for
output.

This code has been thoroughly tested and 95% of the time it runs without
problems. However, every now and then the whole routine just stops running.
It never generates an error and I can't find anything wrong in the code. Most
times if I close everything and start over, it will run all the way through
with no problems.

While this code runs, I'm often doing other things (checkin e-mail in Lotus
Notes, or using Internet Explorer or Access). I believe, but I'm not certain,
that somewhere along the line, I hit some keystroke combination that causes
my Excel VBA to choke. I never have this problem if I don't use any other
programs and just sit back and let it run. However, that's not a great use of
my time.

Does anyone know of any verboten key combinations that could break VBA? Or
something else I could be doing to cause the code to stop?
--
Hmm...they have the Internet on COMPUTERS now!

I don't think you'll get much help without posting at least some of
your code.


Thx,
JP

On Feb 22, 12:21*pm, MDW wrote:
Hello all,

I've got some VBA code in an Excel 2003 file that opens up other Excel
files, updates links, runs some macros, and generates a new Excel file for
output.

I have the same problem and it seems to be tied to use of Office Communicator
2005. When I'm running VBA code that will take a while to complete, I turn
off Communicator.
--
HTH,
Barb Reinhardt



"MDW" wrote:

Hello all,

I've got some VBA code in an Excel 2003 file that opens up other Excel
files, updates links, runs some macros, and generates a new Excel file for
output.

This code has been thoroughly tested and 95% of the time it runs without
problems. However, every now and then the whole routine just stops running.
It never generates an error and I can't find anything wrong in the code. Most
times if I close everything and start over, it will run all the way through
with no problems.

While this code runs, I'm often doing other things (checkin e-mail in Lotus
Notes, or using Internet Explorer or Access). I believe, but I'm not certain,
that somewhere along the line, I hit some keystroke combination that causes
my Excel VBA to choke. I never have this problem if I don't use any other
programs and just sit back and let it run. However, that's not a great use of
my time.

Does anyone know of any verboten key combinations that could break VBA? Or
something else I could be doing to cause the code to stop?
--
Hmm...they have the Internet on COMPUTERS now!