Hello,
I am pressing the metal to get a project out way past deadline on my
Excel 2003 VBA app. I have a routine to programmatically delete and
clear out some text filled ranges and exit but am having problems with
it so I tried to set some debug break points in the code to find the
problem but I get the above Visual Basic error message which didn't
happen before believe in this routine. And it happened earlier trying
to debug another routine which seemed inappropriate. I also tried to
use the debug.assert method but it was just ignored. Right or wrong it
seems this error message is happening too much without apparent
reason. The help on it reads as follows:

"Can't enter break mode at this time


Break mode is the state in which a program is still running, but its
activity is suspended. This error has the following cause and
solution:

You tried to enter break mode, for example, by pressing CTRL+BREAK
(Windows) or COMMAND+PERIOD (Macintosh), pressing the Break button on
the Standard toolbar or the Debug toolbar, or by executing a
breakpoint in the running code.
A change was made programmatically to the project using the
extensibility (add-in) object model. This prevents the program from
having execution suspended. You can continue running, or end
execution, but can't suspend execution. "

I'm not sure what extensibility object model might be involved, but I
was fairly certain I could get break points to work in the routine
before.
If anyone has any experience or suggestions, it would be much
appreciated as I need to get this demo out pronto. Thanks, God bless,
Van

It is normal for some code in VBA to produce the message "Can't enter break
mode at this time". It makes the code harder to debug. I sometimes add
msgbox(...) to the code to help debug these problems. I think debug.print
.... will also work.


"ArielMalek" wrote:

> Hello,
> I am pressing the metal to get a project out way past deadline on my
> Excel 2003 VBA app. I have a routine to programmatically delete and
> clear out some text filled ranges and exit but am having problems with
> it so I tried to set some debug break points in the code to find the
> problem but I get the above Visual Basic error message which didn't
> happen before believe in this routine. And it happened earlier trying
> to debug another routine which seemed inappropriate. I also tried to
> use the debug.assert method but it was just ignored. Right or wrong it
> seems this error message is happening too much without apparent
> reason. The help on it reads as follows:
>
> "Can't enter break mode at this time
>
>
> Break mode is the state in which a program is still running, but its
> activity is suspended. This error has the following cause and
> solution:
>
> You tried to enter break mode, for example, by pressing CTRL+BREAK
> (Windows) or COMMAND+PERIOD (Macintosh), pressing the Break button on
> the Standard toolbar or the Debug toolbar, or by executing a
> breakpoint in the running code.
> A change was made programmatically to the project using the
> extensibility (add-in) object model. This prevents the program from
> having execution suspended. You can continue running, or end
> execution, but can't suspend execution. "
>
> I'm not sure what extensibility object model might be involved, but I
> was fairly certain I could get break points to work in the routine
> before.
> If anyone has any experience or suggestions, it would be much
> appreciated as I need to get this demo out pronto. Thanks, God bless,
> Van
>