How to look backwards from a userform to the calling procedure's error handling

Pretty much exactly as the title says -- can anyone suggest how I can, from within a userform with no error handling, look backwards to the "calling" procedures' error handling? I say "calling" because I understand (or I think I understand) that after firing UserForm_Initialize(), the call stack is going to end, or least break, once it finishes executing it's current line of procedure calls and waits for user interaction. And after user interaction fires an event and there is error generating code in that event or in the line of procedure calls initiated by that event, the furthest down the stack VBA will go to find an error handler is event that fired from the user interaction.

As I understand this (however accurate it may be), it makes sense why the error generated by the user event won't go back to the error handler in the "calling" procedure all the way at the bottom of the stack.


So my question is; is there any way to get around this break in the call stack and tie the error generated by the user event back to the "calling" procedure's error handler, without introducing new error handling? The reason I ask is because I have a project with several complex userforms (with a lot of controls and code) and I don't want to have to introduce error handling in every procedure that needs it just because VBA won't naturally go back to the calling procedure's error handling (as my mind considers the calling procedure to be).


Does that make sense?