ActiveX server via network/DCOM?

[JoeLesker]

I have a Labview EXE that launches an ActiveX server. This works fine when both the client and server are on the local machine. Is it possible for the ActiveX server to be on a separate, LAN-connected machine? Thanks.

-Joe

[Dsun]

Hi JoeLesker,

Hosting the ActiveX server on a separate machine should be possible.  Using the VI Server, you should be able to run LabVIEW VIs across different machines as long as they are in the same network.  I've included a link that describes the VI server.

http://digital.ni.com/public.nsf/allkb/FBD546A08048EA5D86256E8E0027040B

[JoeLesker]

Thanks for the reply.

I should have provided more details. The client application is a VB.Net app, so the interface needs to be environment agnostic. So VI Server isn't really an option.

[Dsun]

When you communicate between the client and the server, do you use the localhost IP?  Also, do you have separate EXEs for your client and server?  If you access the localhost IP it should be a simple matter of changing the IP.

[Kyle97330]

I'm not sure if this is what you're looking for, but have you tried using the .tlb files as described here:

http://digital.ni.com/public.nsf/allkb/38787589F325412186256DE100671A8E

[JoeLesker]

Yes, I am using *.tlb/ActiveX control.  And it works great, if both the server app (the LabView EXE) and the client app (a VB.NET program) are on the same PC.  But I am interested in having the client and server on separate machines, connected via Ethernet.

ActiveX can be utilized for this when extended to DCOM/COM+.  I'm just interested in knowing if this is possible for a LabView EXE, and if there is documentation to enable it.

-Joe

[Kyle97330]

I was under the impression that it was the responsibility of the client app (the VB.NET one, in this case) to connect to the server app.  I'm fairly certain that if the LabVIEW ActiveX server is running on the remote PC, with the DCOM service enabled and the firewall open, the PC is ready to receive.  You just need to set up the client to point towards it, which has nothing to do with LabVIEW.

I could be wrong though... I've never actually tried this in practice.