RE: Excel 2002 debug prompt for all macros
- From: Chris Wieburg <ChrisWieburg@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 7 Oct 2008 09:30:08 -0700
Thomas -
It is a Visual Basic window and the message is "Code Execution has been
interrupted." It then has a button below that is Debug. The user can choose
debug and then step through the macro and it finishes fine. I did just find
out that in a terminal emmulation application we run, the user presses
CTRL+BREAK. If she runs the macro before opening the terminal emmulation
application and pressing CTRL+BREAK her macros work fine. Anytime after she
presses CTRL+BREAK in our
terminal emmulation program, none of her macros work. All of the macros have
VB script in them.
I am under the impression that the CTRL+BREAK key sequence is what is
causing the problem.
Chris
"Thomas [PBD]" wrote:
Chris,.
Is there an error message associated with it? What kind of debug prompt?
--
--Thomas [PBD]
Working hard to make working easy.
Answered your question? Click ''''Yes'''' below.
"Chris Wieburg" wrote:
We have 5 PCs in our department that should all be configured alike. When we
run any macro (includes VBS script) in Excel 2002 on one of the PCs, there is
a debug prompt. On the other 4 PCs the macros work fine. Is there a setting
that could have been turned on that is causing the debug prompt on this
computer?
Chris Wieburg
- Follow-Ups:
- RE: Excel 2002 debug prompt for all macros
- From: Thomas [PBD]
- RE: Excel 2002 debug prompt for all macros
- References:
- Excel 2002 debug prompt for all macros
- From: Chris Wieburg
- RE: Excel 2002 debug prompt for all macros
- From: Thomas [PBD]
- Excel 2002 debug prompt for all macros
- Prev by Date: order of conditional formatting rules
- Next by Date: Re: order of conditional formatting rules
- Previous by thread: RE: Excel 2002 debug prompt for all macros
- Next by thread: RE: Excel 2002 debug prompt for all macros
- Index(es):
Relevant Pages
|