1
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 I did try another, nested Try...Catch, and that did allow me to continue, but not shut down the entire app properly later.
Would appreciate help on this. (I already found out from this forum about putting the MID child on a panel to make it visible... hoping I can "luck-out" again, and, hopefully, be able to contribute myself later.) :o
