Globals are cleared by ending code ("run/reset"); what else happens?

[Oppressed1]

I just put a breakpoint on End Sub, went alt-R,R, and now MyGlobalString is "" whereas had I instead gone F5 or F8 it would be "foo" as assigned earlier. (The variable was defined atop the module, public MyGlobalString as string) Also, a form control's value that normally would persist when I .Show'd the form again is lost by breaking and ending code.

Are there other implications of terminating code? I always thought that all I had to worry about was restoring states like Calculation mode and closing things that obviously need to be closed. What else happens?

( And while I'm thinking about it, I wonder which "state" variables do I really need to worry about restoring anyway? I seem to observe that some always return to normal regardless of how code ends (.ScreenUpdating) and some don't (.Calculation). )

I do note on https://msdn.microsoft.com/en-us/vba...tart-execution
"You can restart execution from break mode. Restarting returns the code to a newly initialized state, resetting all variables and removing any suspendedprocedures from memory." (By "restarting" it means to restart code by alt-R, R and then running code again)

[Oppressed1]

I've reset code a million times in my life. Another million times I've effectively done so by hitting alt-F4 when in break mode (thus asking to close the VBA window) and "OK" to the messagebox warning me that code will end. Now I'm thinking - after religiously doing it one way for 2 million times - if I should just go to the immediate window and type end and hit enter instead?!

[Oppressed1]

Errrr, no, executing End does the same thing. And you can't go Exit Sub in the immediate window. Looks like I have to awkwardly highlight "End Sub" and set as next statement and run. Is that really what is required to preserve static variables?

[Oppressed1]

So I end up with 3 questions:
1. What else happens besides static variable clearing when you reset code?
2. What "state" variables persist on normal termination, yet change on code reset?
(bonus: what state variables don't persist anyway, e.g. .ScreenUpdating ?)
3. Is there a better way to "normally" terminate code, preserving statics, than the cumbersome "setting next statement" ?

[Oppressed1]

Bump .

[SpacePirate]

I've run into this same problem before in both Excel and Access.

The best way I've been able to get around it is putting a label one line above End Sub, and then dragging around a "Goto GetOut" statement to wherever I am debugging.

It's annoying to do. I'd love to know if there's a better way.