http://support.microsoft.com/kb/947670

I found the answer here in case anyone is interested to know the end result of this. The OLE error was caused by some Fox runtimes that were out of whack. There were SP1 runtimes in my windows system folder while microsoft shared folder had SP2 runtime files. Not really sure how that happened but it was easy enought to fix once I found this KB article.

Thanks to all who helped with this!

-Don


>>>>I'm trying to create a multi-threaded DLL that will be used to pass a dataset to C# .NET via XML. I have created my .DLL in VFP and then I went to test it by issuing this command from the command window:
>>>>
>>>>

>>>>oDemo = CREATEOBJECT("comtest.VFPCom")
>>>>

>>>>
>>>>After issuing that command I get an OLE Error. I'm not sure there is enough in that error for anyone to know what I'm doing wrong, but I was wondering if anyone has any pointers on how to debug a COM server like this?
>>>
>>>Have you tried AERROR() to find out what error the server is throwing? Also, consider using COMReturnError() in the DLL's error handler to get detailed info back.
>>>
>>>Tamar
>>
>>
>>Hi Tamar,
>>
>>Since my original post I have created an Error procedure in my project which I have placed inside the define for my OLEPUBLIC class. But it doesn't appear that when I try testing it in VFP with the CREATEOBJECT that it even gets to my error handler code. It is given the OLE error before that even occurs. Any other thoughts would be greatly appreciated.
>
>What happens if you try to instantiate your class as a regular VFP class, not an OLEPublic? That is, use CREATEOBJECT() or NEWOBJECT() directly on the class.
>
>Tamar