I've recently been working on a project that uses a COM EXE that runs in a separate process. When updating it I have to make sure to be running VFP "as an administrator", otherwise the build process does not register the COM EXE.

I haven't tried it with a COM DLL or MTDLL but it might work the same way. Easy enough to test, anyways.

>Excellent thought, but when you build the DLL in VFP it registers automatically. I have confirmed it is registered by adding it as a reference in Visual Studio 2012 project. My comtest.dll shows up in the list of registered libraries.
>
>thanks,
>-Don
>
>>I *think* that means you need to register the DLL (use regsrv32.exe)
>>http://support.microsoft.com/kb/249873#method1
>>
>>>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?