The demos I have seen regarding creating an ActiveX EXE (Out of Process) component all state that the application can reside on a different processor than the ActiveX EXE it is using. Anyone ever do this before? None of the samples say how this can be done. How do you register a component on a different processor?

The Reason I need this is I have an ActiveX EXE which provides functions to applications sending formatted messages out the serial port (The commands are used to send messages to an inventory carousel). Some customers want to run this application on Windows Terminal Services. Terminal Services 2000 (RDP 5.0) does not support Local Serial Ports. My thought is if the application (which of course would run on the Terminal Server)opened the ActiveX EXE on the actual Client, I would be utilizing the Local Serial Port.

Any ideas would be appreciated. I realize I could wite a Sockets program that does communicates for me but if I don't need that overhead, why bother!

Thanks for your thoughts!