>>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?
>
>Steve, you have to copy your COM object .EXE .TLB. and .VBR files on the worstation and register your COM on the workstation with:
>
>CLIREG32.EXE yourcomobject.VBR
>
>If CLIREG32.EXE is not accessible, just search for it - you can find several copies under your Visual Studio installation, or copy it from another PC.
>
>Then run DCOMCNFG.EXE on the workstation and make sure that under properties for your COM the Location tab shows: "Run application on the following computer" and \\MyServer as a name. (you will be also asked about it when you run CLIREG32.EXE)
>You also need to configure the "Default Security" in DCOMCNFG on the server PC to setup the Default Launch Permissions and Default Access Permissions to add the "Network" user. The custom permissions also may be configured individually for your COM server in its Properties/Security tab.
>Security configuration is up to you.

Nick-

The steps you are describing will work, but should not be necessary. After performingthe steps you describe, the component would be callable with only CREATEOBJECT("ProgID"). But CREATEOBJECTEX does not require that the server component be registered on the client machine.

Interestingly, in VFP7, CREATEOBJECTEX in VFP7 takes an optional third parameter, an interface GUID that allows early binding with a single function call.