>Hi Mark,
>
>>But what if there are multiple olepublic classes in the dcom component? Which one is going to run?
>
>The ProgID and class ID are specific to an olepublic class. If you have multiple classes in a single DCOM server, you end up with multiple class IDs and registry entries. All of them point to the same EXE.
>
>The local registration was necessary for one reason. When you specify a ProgID like "MyServer.Class1", Windows cannot pass that on to the remote server. The remote server only accepts class IDs. Therefore, Windows used the local registration on the client to look up the class ID given the ProgID.

Hi Christof,

I've built a DLL called DataRetriever with only one class DataRetriever. I registered DLL on the server.

I'm trying
o = createobjectex("DataRetriever.DataRetriever","\\jzanus8")
Returns class not registered

o = createobjectex("DataRetriever.DataRetriever","jzanus8")

Class not registered

o = createobjectex("DataRetriever.DataRetriever","jzanus8D")

o = createobjectex("DataRetriever.DataRetriever","jzanus8_D")
o = createobjectex("DataRetriever.DataRetriever","JZANUS8_D")

The RPC server is unavailable.

I could not find examples of calling CreateObjectEx function to make it work. Our idea is to have DLL on the server to return data as XML to the local PC. Do you think it should work?