Are there drawbacks to using the "End" statement?

[dmasters4919]

A while ago when I was trying to figure out how to end a macro completely if something goes wrong in a sub that was called by another main sub, I ended up finding the End statement. It seemed like the cleanest way to stop everything, without having to put an exit sub statement in both subs. Today I was on the MSDN help page for the end statement and it suggests using it sparingly. I haven't run into any trouble so far and it seems like a relatively simple statement. Going forward I may instead start raising user defined errors to stop the process instead.

Does anyone have an opinion on this?

[Andy Pope]

Yes, use it sparingly.
As it says it will reset all public variables. Whilst this may not directly impact your coding it may affect code in any addins you use.

Have a read of the help on End witin VBA.

[dmasters4919]

Yes, use it sparingly.
As it says it will reset all public variables. Whilst this may not directly impact your coding it may affect code in any addins you use.

Have a read of the help on End witin VBA.

Thank you. Let's say I instead raise a user error. If the user hits "End" instead of "Debug" when the dialog box comes up, do you know if this would also reset all public variables?

[Andy Pope]

Yes it would.

why not handle the error(s). you can capture it and report information if relevant without relying on the end/debug dialog.