>>>>>>>>>I have a VFP COM object that I use on my web pages with no problem. It is installed and registered on my web server. I am now trying to do a CreateObjectEX('{8795FE62-4127-11D4-B8A9-005004B2CDCF}','\\MyServer') from a workstation and it always fails with "Class not registered" errors. What do I need to do to be able to instantiate this object from a remote workstation?
>>>>>>>>
>>>>>>>>Where did you get the CLSID that you passed? Are you sure it's the right one? What ou are trying should work, as long as the component is registered on the remote machine, the CLSID is right, and the machine name is resolvable.
>>>>>>>
>>>>>>>
>>>>>>>I cut and pasted the CLSID straight from the .VBR file that is sitting on the server. I also cut and pasted the machine name from my Explorer window. The COM object works fine, the web site uses it all day long.
>>>>>>
>>>>>>Can you double check it in the registry? The CLSID you are using should be listed in HKCR\CLSID, and point to the EXE in question. Wait- it is an exe right?
>>>>>
>>>>>No, it's a DLL.........
>>>>
>>>>You can't run a dll through DCOM unless its in an MTS Package or COM+ application. DLLs run in-process...
>>>
>>>Or unless your DLL is instantiated by another out-of-process COM EXE on the same server, which could be done by calling the method in that COM.
>>
>>Yeah, but why go to all the trouble? Just use an exe or MTS.
>>
>>That's basically what MTS/COM+ does. It sets up a 'surrogate' process for your component by manipulating the component's registry settings so that when someone attempts to instanciate the object, MTS is called instead, and it in turn calls your component, and all calls are made through the MTS context.
>
>Does that have any affect on my current web apps that use the component?

Are they ASP (late-bound)? If so, then no. Is the component used heavily? If so, you might want to wander over to www.west-wind.com and read Rick's paper on MTS and VFP components. He raises some scalability issues that you should be aware of.