>Ken -
>
>You are right - that error is mentioned in the article. I only receive that error when I try to instanciate the object while my colleague is modifying the registry. I am getting a different error the rest of the time -
>Error number 0x80040154:Class not Registered.
>
>
>Sara

Sara,
I am trying to do the same thing. I followed the instructions in Chapter 16 of the VFP manual for remote automation and everything works BUT ONLY IF the client machine I am trying to register the remote object on has clireg32, racmgr32, etc. already on it (which this client does because of having VStudio installed) However, I want to register this COM object on a machine that does not have VStudio (It's a web server with IIS, etc.) It does not have clireg32 so I copied it over with autprx32.dll. It registers fine and the registry entries tie out to the other client machine that works. It also will instantiate the top level application class on the host machine (I can see oApp.Name), but as soon as I make any method calls that should instantiate internal classes within the application, I get "ActiveX component can't create object, etc..." It doesn't matter what the client program is (VBScript, VBA, etc.) What am I missing? How do I get the remote utilities (DCOMCONFIG, racmgr32, clireg32) installed without installing Visual Studio on the client? This is very frustrating to say the least.
Also, these are all NT Workstation machines.

Randy