> Thread #817873 Message #818124.

Thanks Sergey. Once again, I am indebted to you.
I tried that code snippet by Cetin and it seems to work great.


>You can check registry at the beginning of your application. See Re: How to verify if an OLE control is installed... Thread #817873 Message #818124.
>You can also subclass a form with control and use TRY...ENDTRY to see if it can be instantiated.
>You may try to use _comdlg class in the FFC\_system.vcx. It's a VFP wrapper for WIndows API that OCX uses. Check Descriptive File Types with PUTFILE() Thread #574248.
>
>>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.
>>
>>
>>