DCOM = nightmare

Hi, is it just me or is DCOM a complete nightmare when combined with Win2k security? Without getting into network security API I wasn't able to establish a constant method to get remote automation to work on different computers.

What are everyone elses experiences?

DCOM indeed have some problems.
i don't know what your system looks like, but i prefer not to use ActiveX EXE server for accessing remotely.
the most problematic thing in EXE server is to inspect on it's process, u don't have much control over it to determine how many active users using the server, how many threads the server hold, the period of the method that invoked etc.
of course u can add such features to your server, but it's non trivial task.
the other problems regarding DCOM configuration, registry updating etc.
u can following the KB from ms support here http://support.microsoft.com/default...;en-us;269330.
my recommendation is to use COM+.
COM+ solve most of the problem i just mention, and it provide much more functionality to your COM objects.
u can very easily propagate proxy of your COM objects through export option in Component Services Snap In.

thanks deja... since my project time is running out I've decided to abandon the client/server/db design and do straight client/db via ADO...