Hi Yuri,

My bad, sorry, I didn't explain fully. Here is a more detailed explanation:

I need the form to run because the new control is optional funcationality. The purpose of the form is to create a zip backup and the new control will now PGP encrypt the zip file if a checkbox is checked.

If the user didn't install an updated Workstation install, the necessary ActiveX control didn't get installed. When they open the form, they get the OLE error as mentioned. They can Ok that message and the form works fine, the functionality that the ActiveX Control is used for is easily bypassed (I just disable a checkbox accordingly).

Due to the circumstances I'm faced with right now (quarterly release that is in final QA that must go out in a few hours), all I needed was how to trap that error and present a custom messagebox. Everything else is taken care of.


Thanks again,


- Brian


So, why do not you want to put this code in the form load and return .f. from there closing form and dispaying message you want?
>
>>Hi Yuri,
>>
>>Thanks, this is helpful for checking prior to calling the form. Unfortunately I need to check and by-pass the default error message between the Form.Load and the time the Control.init tries to fire. I.e. The form was already called.
>