A. Rafiq's reply / answer is just exactly what I was looking for as well. I'm using it with VBA for an Excel application.
Note that the differences between this and the "not compiled" VI is that the application is the compiled application name, versus LabVIEW.
Additional information:
Remember that when you build the application, it puts the VI(s) in a wrapper app, which requires the Run-Time Engine.
In order to access the VI, you have to get a reference to it. Doing this starts the app.
Now the VI's methods and properties are exposed.
With the GetControlValue and SetControlValue
methods of the VI you can access all of the controls on the front panel.
Remember that the values returned from the GetControlValue method are of type Variant.
If you find you h
ave some trouble getting data in or out of your (LabVIEW) ActiveX server app, you can also easily write a VI to access the server.
Remember that if you want to run these, the ActiveX server (LabVIEW) and the VB client app, on a remote machine you must:
Install on the target machine the LabVIEW RTE (which you can include with Application Builder.
Running the server app once on the remote machine before running the client is a way for the server app to register itself (at least in LV 5.1).
