Statement to execute code on “Break”

[Glory]

I’d like to be able to execute some code when VBA enters “Break mode”. Is there a statement to accomplish this?

 

[tusharm]

You could execute code through the Immediate window but other than that you are in *break* mode -- by definition code execution has been *interrupted*.

I’d like to be able to execute some code when VBA enters “Break mode”. Is there a statement to accomplish this?

 

[Glory]

I'm thinking something like "on error".

I’ve got this macro that takes like five minutes to run. More importantly, it disables screenupdating using a windows API function (found here).
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o> </o>
I want the user to be able to break the code without hopping into Excel’s VBE, if at all possible.

Nothing comes to mind?

 

[tusharm]

I allow the customer to interrupt a long running procedure through the use of a userform shown modeless. The userform has a 'cancel' button that, when clicked, sets a global boolean to true. The code checks the state of this variable "every so often" and if it sees it is true, the code gracefully stops.

You can see the above in action in the TM Directory Listing shareware product. Visit http://www.tushar-mehta.com/excel/software/dirlist/index.html

But, then, I am not a believer of messing with the customer's environment with APIs that disable screenpdating (or other such features). So I don't know if my solution will work for you.

I'm thinking something like "on error".

I’ve got this macro that takes like five minutes to run. More importantly, it disables screenupdating using a windows API function (found here).
<?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o> </o>
I want the user to be able to break the code without hopping into Excel’s VBE, if at all possible.

Nothing comes to mind?

 

[Glory]

The only reason I’m using the API is because I need to suppress “Now Printing” dialogue windows… otherwise hundreds of these would be appearing as the macro ran its course.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o></o>
<o> </o>
Do you have any suggestions for suppressing these dialogues, that do not require disabling screenupdating (which is an admittedly dicey angle of attack)?

 

[tusharm]

Check if what I suggested works with the API you are using.

The only reason I’m using the API is because I need to suppress “Now Printing” dialogue windows… otherwise hundreds of these would be appearing as the macro ran its course.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o></o>
<o> </o>
Do you have any suggestions for suppressing these dialogues, that do not require disabling screenupdating (which is an admittedly dicey angle of attack)?

 

[Glory]

Your suggestion combined with an error handler did the trick. Needs the handler because setting the global boolean to exit the macro causes an error wherever the user triggered the hotkey that controls the exit command. Thanks for the suggestion.

 

[tusharm]

Your suggestion combined with an error handler did the trick. Needs the handler because setting the global boolean to exit the macro causes an error wherever the user triggered the hotkey that controls the exit command. Thanks for the suggestion.