Hi,

I am running the code to test it and it is breaking due to an error but when
the debugger opens it puts up a dialogue box with the message:

'Can't execute the code in break mode'

Anyone any idea why this annoying message has started occuring when it
breaks (prior to this it just opened the debugger at the offending line
without the annoying dialogue box).

Any help appreciated, Mark

look at this site:

http://support.microsoft.com/kb/213672

"Mark Stephens" wrote:

> Hi,
>
> I am running the code to test it and it is breaking due to an error but when
> the debugger opens it puts up a dialogue box with the message:
>
> 'Can't execute the code in break mode'
>
> Anyone any idea why this annoying message has started occuring when it
> breaks (prior to this it just opened the debugger at the offending line
> without the annoying dialogue box).
>
> Any help appreciated, Mark
>
>
>

Hi JLG,

That certainly highlights the problem and tells me what to do when it
happens (which I do know) what I need to find out is why it is happening and
how to stop it telling me it cannot operate in break mode (which is implicit
in that it has broken due to an erro for me to debug).

Anyone else?

Regards, Mark


"JLGWhiz" <(E-Mail Removed)> wrote in message
news:8F15DFAD-71A7-4761-9390-(E-Mail Removed)...
> look at this site:
>
> http://support.microsoft.com/kb/213672
>
> "Mark Stephens" wrote:
>
>> Hi,
>>
>> I am running the code to test it and it is breaking due to an error but
>> when
>> the debugger opens it puts up a dialogue box with the message:
>>
>> 'Can't execute the code in break mode'
>>
>> Anyone any idea why this annoying message has started occuring when it
>> breaks (prior to this it just opened the debugger at the offending line
>> without the annoying dialogue box).
>>
>> Any help appreciated, Mark
>>
>>
>>

....Is the line that is breaking with the error trying to execute another
function. Post the line where it is breaking.

"Mark Stephens" wrote:

> Hi JLG,
>
> That certainly highlights the problem and tells me what to do when it
> happens (which I do know) what I need to find out is why it is happening and
> how to stop it telling me it cannot operate in break mode (which is implicit
> in that it has broken due to an erro for me to debug).
>
> Anyone else?
>
> Regards, Mark
>
>
> "JLGWhiz" <(E-Mail Removed)> wrote in message
> news:8F15DFAD-71A7-4761-9390-(E-Mail Removed)...
> > look at this site:
> >
> > http://support.microsoft.com/kb/213672
> >
> > "Mark Stephens" wrote:
> >
> >> Hi,
> >>
> >> I am running the code to test it and it is breaking due to an error but
> >> when
> >> the debugger opens it puts up a dialogue box with the message:
> >>
> >> 'Can't execute the code in break mode'
> >>
> >> Anyone any idea why this annoying message has started occuring when it
> >> breaks (prior to this it just opened the debugger at the offending line
> >> without the annoying dialogue box).
> >>
> >> Any help appreciated, Mark
> >>
> >>
> >>
>
>
>

What the article states is that the message only appears if you are in break
mode when you try to start another macro from the keyboard or from the run
command using the macro dialogs box. So in simple words, you have a live
macro somewhere that is in break mode while you are tring to start a new, or
even the same, macro. Open the VBE and look for the macro that is in break
mode and either end it or click the continue control to finish running it.

I don't know how to explain it any differently.

"Mark Stephens" wrote:

> Hi JLG,
>
> That certainly highlights the problem and tells me what to do when it
> happens (which I do know) what I need to find out is why it is happening and
> how to stop it telling me it cannot operate in break mode (which is implicit
> in that it has broken due to an erro for me to debug).
>
> Anyone else?
>
> Regards, Mark
>
>
> "JLGWhiz" <(E-Mail Removed)> wrote in message
> news:8F15DFAD-71A7-4761-9390-(E-Mail Removed)...
> > look at this site:
> >
> > http://support.microsoft.com/kb/213672
> >
> > "Mark Stephens" wrote:
> >
> >> Hi,
> >>
> >> I am running the code to test it and it is breaking due to an error but
> >> when
> >> the debugger opens it puts up a dialogue box with the message:
> >>
> >> 'Can't execute the code in break mode'
> >>
> >> Anyone any idea why this annoying message has started occuring when it
> >> breaks (prior to this it just opened the debugger at the offending line
> >> without the annoying dialogue box).
> >>
> >> Any help appreciated, Mark
> >>
> >>
> >>
>
>
>

Just an added note. If the macro is entering break mode due to an error,
then you need to fix the code that causes the error to keep from getting the
"Can't execute" message. Also, if it is entering break mode because there is
a manual break point applied, then remove the manual break point.

"Mark Stephens" wrote:

> Hi JLG,
>
> That certainly highlights the problem and tells me what to do when it
> happens (which I do know) what I need to find out is why it is happening and
> how to stop it telling me it cannot operate in break mode (which is implicit
> in that it has broken due to an erro for me to debug).
>
> Anyone else?
>
> Regards, Mark
>
>
> "JLGWhiz" <(E-Mail Removed)> wrote in message
> news:8F15DFAD-71A7-4761-9390-(E-Mail Removed)...
> > look at this site:
> >
> > http://support.microsoft.com/kb/213672
> >
> > "Mark Stephens" wrote:
> >
> >> Hi,
> >>
> >> I am running the code to test it and it is breaking due to an error but
> >> when
> >> the debugger opens it puts up a dialogue box with the message:
> >>
> >> 'Can't execute the code in break mode'
> >>
> >> Anyone any idea why this annoying message has started occuring when it
> >> breaks (prior to this it just opened the debugger at the offending line
> >> without the annoying dialogue box).
> >>
> >> Any help appreciated, Mark
> >>
> >>
> >>
>
>
>

"JLGWhiz" <(E-Mail Removed)> wrote in message
news:869ADF1D-DC69-4112-A93F-(E-Mail Removed)...
> Just an added note. If the macro is entering break mode due to an error,
> then you need to fix the code that causes the error to keep from getting
> the
> "Can't execute" message.

Or press Stop.

Tim

Also, if it is entering break mode because there is
> a manual break point applied, then remove the manual break point.
>
> "Mark Stephens" wrote:
>
>> Hi JLG,
>>
>> That certainly highlights the problem and tells me what to do when it
>> happens (which I do know) what I need to find out is why it is happening
>> and
>> how to stop it telling me it cannot operate in break mode (which is
>> implicit
>> in that it has broken due to an erro for me to debug).
>>
>> Anyone else?
>>
>> Regards, Mark
>>
>>
>>