Server must exist both on the client and the server (or at least the typelibrary) if you use the ProgID (someserver.someclass). If you use the CLassID for the server that requirement goes away.

You also will have to deal with access permissions to the server. By default Windows 2000 doesn't allow remote access to any objects even by administrators. You need to configure this with DCOMCNFG.

Take a look at:

http://www.west-wind.com/articles.asp and look at that Internet Enabling article there...

+++ Rick ---

>Hi all,
>
>I have a custom object which basically performs selects and returns results as objects, it works very well in my tests instantiating it with set classlib to../createobject(xxx); it works very well as a local COM out of process (exe) server, too.
>
>Now I want to use it as a COM server in a remote machine but I CAN NOT do it. I simply don't know how to use CREATEOBJECTEX() :(
>
>Yes, I had read the help file, and had tried in every way possible, but still I don't know how to make it work.
>My project is in a network drive in our development server (machine,-to avoid confussions-), so usually I am creating the exe file there. As I said, I can instantiate it from there in my machine and is working fine.
>How to instantiate it from any station and make the COM server execute in our development or data server (machines)?
>
>I'll be eternally grateful if you can give me a detailed 'for dummies' step by step explanation on how to deploy/install on the stations and the server machine and deal with DCOM security.
>Even better for a piece of code to make it from a central location. :)
>
>
>TIA.
>
>Agustin.