Check also VFP2C32 File #28338

>I've about decided that this whole OCX thing is a bunch of crap.
>
>On a test machine (no development environment), I have found that even if the OCX is installed, it seems that you cannot easily test for it. As you inferred earlier, this construct:

>CREATEOBJECT("MSComDlg.CommonDialog.1")

>always fails on an "unlicensed" machine.
>
>The alternative: If you just go ahead and use the control on a form but the control is not registered on the machine, you've got to capture the OLE error at a weird time (when the form is instantiating).
>
>Can you tell me, if you put the control on a form, how do you create a try/catch construct to "catch" the failure of the control to instantiate on the form? Basically, I need to catch the OCX failure when it's not registered on the machine so that I can fall back to GetFile().
>
>What do you recommend? Thanks gain.
>
>
>