I have built one program which worked as an ActiveX (Ax from now on) server.
Did not check what it did with registry (just build a sample proggy and
check it out yourself), but it exposed the same properties, methods, events
as labview. You would use it as every other Ax server, probably by opening
a reference to it in VB like you would for Excel.
I remember that if I would rebuild executable bunch of times, then after the
first build *.tbl file would not be recreated (this is under LV501). That
caused problems because I had deleted the old one. *.tbl file lists
properties, etc. exposed by the Ax server.
There are couple of examples of VB talking to Labview using Ax. They are on
NI website in downloads section. I am pretty sure that you could use those
to make VB to ta
lk with your app.
I think that executable registers itself after its first execution, but do
not know for sure.
wrote in message news:7tnup8$lqm$1@nnrp1.deja.com...
> (LabView)
> I am trying to build a simple standalone ActiveX
> Server to use in VB and Excel 9x. It will be
> ported to a Win95 computer that knows nothing
> about LabView. Is there any clear
> documentation/examples to walk me through the
> process, or at least answer the following
> questions?
>
> What can I expect in the development registry?
> What goes in the client machine registry?
> How would I access the control from VB?
> How would I access the control from Excel?
> How can I keep the development registry clean?
> Thanks
> Dave
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.