Multiple instances of a subVI - problem if running as executable

Question

Hello LabVIEW gurus,
I have written an application, which uses a VI-template to create multiple instances of this subVI which are
running independently. I use 'Open VI Referece' and the 'Call By Reference Node' VIs. My application works
fine if it is executed in the LabVIEW development environment.
But if I use the Application Builder to create a stand alone program, the 'Call By Reference' method seems
not to work. The program works without any error message, but the subVIs created by call by reference
deliveres no results. I suppose the subVIs are not created properly.
Has anybody an idea or hint to solve that problem. Are there any known issues with 'Call By Reference Node'
and 'executables'. Are there special points to pay attention for?
I have that problem with LabVIEW 7.0 and 7.1 (Windows2000 and WindowsXP(SP2))
Thanks for any hint that could be helpful.
Steffen

Answer 1

Sorry for the obvious question but did you include the templates as
dynamic VIs when building the application? Since these VIs are not part
of the Top Level hierachy, they have to be include explicitely as
dynamic VIs.
By the way, when VIs are included as dynamic VIs they are put in the
internal LLB of the executable file. When opening the VI reference,
that internal LLB is first looked into for a VI of that name and if it
is found there the actual path is ignored. The internal VI is opened so
you don't have to care about absolute paths when using inluded dynamic
VIs e.g. you can leave paths used during development. The actual path
is important only when the referenced VI is located outside the
executable.
LabVIEW, C'est LabVIEW