Excel 2002 debug prompt for all macros

C

Chris Wieburg

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
 
T

Thomas [PBD]

Chris,

Is there an error message associated with it? What kind of debug prompt?
 
C

Chris Wieburg

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 said:
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 said:
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
Click to expand...
Click to expand...
 
T

Thomas [PBD]

Chris,

The CTRL+BREAK is what is causing the issue. It basically stops the script
mid-run (interrupt), and will return that exact error message. It would be
the same error if a non-stop loop was enabled and you wanted to break it.
CTRL+BREAK is universal and will work whether she is looking at the Excel
document or not, so if she can avoid it, it is recommended.

--
--Thomas [PBD]
Working hard to make working easy.
Answered your question? Click ''''Yes'''' below.


Chris Wieburg said:
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 said:
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 said:
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
Click to expand...
Click to expand...
Click to expand...
 
C

Chris Wieburg

Thomas -

Thanks for the confirmation. We changed her login for our mainframe so she
gets a yes/no prompt rather than her needing to press CTRL+BREAK and that
seems to have worked better.

Chris

Thomas said:
Chris,

The CTRL+BREAK is what is causing the issue. It basically stops the script
mid-run (interrupt), and will return that exact error message. It would be
the same error if a non-stop loop was enabled and you wanted to break it.
CTRL+BREAK is universal and will work whether she is looking at the Excel
document or not, so if she can avoid it, it is recommended.

--
--Thomas [PBD]
Working hard to make working easy.
Answered your question? Click ''''Yes'''' below.


Chris Wieburg said:
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 said:
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.


:

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
Click to expand...
Click to expand...
Click to expand...
 
Top