> Active-X is essential an alternate mechanism of interacting and
> controlling LabView. Equivalent access to the graphic user interface is
> provided. The ability to load, run, and detect error of "vi" programs is
> provided.
>
> TCP/IP and UDP interconnectivity is essentially a mechanism to
> communicate with a running "vi" program. Not as much, if any, access to the
> upper controller "LabView Environment" is supported.
>
This is pretty close. The VI Server is what exports the
functionality of being able to execute, modify, and generally
operate LV programmatically.
The VI Server is exported through both ActiveX and through
built-in icons which basically use TCP/IP.
So, ActiveX can do what you are getting at, but lots more
as well. Both it a
nd TCP are a mechanism for exporting
data and functionality. They are lower level mechanisms
that the VI Server is exported over as well as being
available for other things.
Greg McKaskle