jason clark wrote in message
news:8tn8ek$nc3$1@uranium.btinternet.com...
> I have created a VI that opens the Active X controller and initiates the
> driver, the control reference is then passed out to another VI via a
> terminal, along with an error cluster.
>
> Thinking about the project, this is probably not the best way to share
this
> resource.
I dunno- sounds fine to me. What's the problem?
> Should I be;
>
> a) Write a complete vi library that keeps the Active X reference local,
> with wrapper functions for the methods and properties of the control?
Uck, no- that is essentially duplicating the functionality of the Labview
ActiveX stuff, which is itself a set of wrappers to give a unified front
end, I assume.
> b) Make the cont
rols reference a global variable, and try and make
> connections that way. I did try this today, but the Active X invoke node
> wouldn't work, when I passed it the reference from the global.
It should work, but you need to make sure you write the reference to the
global before anything reads it. You also have to be aware that when no VIs
are executing, various internal cleanups take place, in which all open
references are closed. This means that if you manually run one program to
write the reference, then when that stops manually run another to read and
use it, the reference won't be valid.