Situation:
1. VB.net MID with ActiveX on MDI Child
2. On error loading a doc into the ActiveX, the failure prevents disposal of the MDI child, despite using Try...Catch. Must restart the app, and the app doesn't easily shut down, on top of that.
My problem is NOT the ActiveX error itself. I could fix it, if I could react to it, rather than having it freeze my system.
One approach might be a nested Try...Catch...