Hi Alexander!

I tried using the latest version of OLEDBFOX.DLL that you sent me in place of the latest version of VFPCOM.DLL and IT WORKED! No more error!

Thanks a million! ;-)

It is my understanding that the latest version of VFPCOM.DLL was supposed to be compatible with VFP8. However, I believe this new issue demonstrates that it's not quite there yet.

Thanks again, Alexander! And Thanks for OLEDBFOX.DLL! :-)

:-)

Randy

>Greetings Alexander!
>
>>It may be VFPCOM, OleDbFox or some of bbControls, for example.
>
>I am using VFPCOM to generate the ADO recordsets. I will try using OLEDBFOX and see if I still get the error in VFP8.
>
>Thanks for the tip! I greatly appreciate your input on this!
>
>:-)
>
>Best regards,
>
>Randy
>
>>Hi Randy,
>>
>>These error messages usually generated by third-party ActiveX controls or FLLs, built with use of FoxAPI. It looks that you have used such control or FLL, which is not compatible with VFP8. It may be VFPCOM, OleDbFox or some of bbControls, for example.
>>
>>>Correction. After looking at the error message again, it says,
>>>
>>>"This OCX must be hosted in Visual FoxPro"
>>>
>>>I don't know if that makes it any clearer or not. ;-)
>>>
>>>Thanks,
>>>
>>>Randy
>>>
>>>>Greetings All,
>>>>
>>>>Have an application where I'm using Crystal Reports 8.5 RDC. Have run into the following error when running the EXE from outside the VFP8 environment (in both VFP8 pre and post SP1) under Windows XP Pro, SP1a:
>>>>
>>>>"This OCX only runs in Visual FoxPro"
>>>>
>>>>This error does not occur when the EXE is run within VFP8 (i.e. DO sample.exe). Also, this error does not occur when running the external EXE under Windows 2000.
>>>>
>>>>When compiling an EXE under VFP7, the error does not occur when running the external EXE in XP Pro. It only occurs in VFP8.
>>>>
>>>>Since the error only occurs when running outside of VFP8, it is hard to isolate exactly where the error is occuring. I have placed WAIT WINDOW calls at various points in the code in attempt to determine if it error was occuring during instantiation of RDC or during preview process. From what I can determine, the error does not seem to occur during the instanitation of the RDC or preview control objects, but occurs later.
>>>>
>>>>Any ideas would be greatly apprecicated.
>>>>
>>>>TIA,
>>>>
>>>>Randy McAtee