I've been searching left and right for this answer, but all I seem to find is just ways to do error handling. Anyhow, I'm creating a custom error handler for my project and while some custom userform/message box solution with Err.Number and Err.Description printing is more user-friendly than the default debug dialog box (the Continue/End/Debug/Help-one), I'd like to sustain the function from the Debug-button (where you are presented the highlighted row which caused the error in VBA editor).

So what I'm after is a userform or a message box solution, where the user can either quit or continue to debug the error in question in VBA editor. The problem is however that I don't know how to create this latter functionality. If I use for instance
If MsgBox("Proceed to debug?", vbCritical + vbYesNo, "Error") = vbYes Then Debug.Assert False
The code will surely open the editor, but it doesn't highlight the initial cause of error, just the debug call. Is this kind of functionality possible to achieve or do I just have to settle for the Debug.Assert?