Use an ActiveX EXE on different PC

[dbarr]

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!

[Cander]

I think you mis-read. ActiveX Exe runs in a different PROCESS...not on a differnt processOR.

yoi can isntantiate an object the physically resides on a nother computer within the same network by specifying the servername parameter for CreateObject, but it still will run on the running clients machine

[dbarr]

I found this in the MSDN, which leads me to believe I can run the component remotely:

If you’re creating an out-of-process component, open a new ActiveX EXE project. Reasons to create an out-of-process component include:
The component can run as a standalone desktop application, like Microsoft Excel or Microsoft Word, in addition to providing objects.


The component can process requests on an independent thread of execution, notifying the client of task completion using events or asynchronous call-backs. This frees the client to respond to the user.


If you’re using COM or Remote Automation to run components on remote computers (Enterprise Edition only), some components may need to be .exe files.