I've just finished searching here at UT to find a decent example of registering an Out-of-Process server. The EXE is built and on the server. That is registered there just fine. The VBR and TLB files are there also. One can activate it from the server. But, cannot seem to activate it from a client.

Could someone please list the steps....with far better description that MSDN regarding registering this beast so the client can see it.
CLIREG32 gets run.... but do you point it to the VBR on the server or do you copy the VBR to the client and point it there. If to the client, in what folder?

And need to know what to answer for:

D COM or Remote Automation - my choice would be remote.

NetWork Address - no idea what to put here...the person on site is getting some network assistance.

HTTP or IP_TCP - my choice would be IP_TCP but I don't know. I'm not at the site where they are tyring to register this so I that means I don't know the other options that may be available at the site.

The server is developed here with the code (and exe) sent to the site.
Do they need to rebuild the exe? What do they need to do each time they might get a new version from me?

Ugh....any assistance here would be greatly appreciated.

Thanks,
Steve