LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

A VI called by reference with a express VI included does not work!?

HI Michael,

See attached zip new bld file "appl2.bld".

After un-checking the "disconnect" and doing a save as from the builder, the app runs fine.

I have added some indicators that show that the Express VI was loading a unique instance of a hidden VI (?system?).

Un-checking the box did the trick.

This does sound like the issue Michael A. had reported.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 21 of 26
(991 Views)
Note:

I had some difficulty in getting the check box value to save. That is why I did the ave as.

That may be a new bug.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 22 of 26
(989 Views)
DIsregard my comment about the saving. It seems OK now that I am paying attention.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 23 of 26
(979 Views)
Thanks Ben,

Now I know!!!

Best Regards,
Michael
0 Kudos
Message 24 of 26
(973 Views)
So do you agree that this is not a new BUG but appears to be a new variation on the "disconnect typedef..." issue.

If so my work is done here and I will NOT be reporting this issue.

Thanks for the adventure. I learned;

1) LV exe's can can non-exe VI provided they are compiled in the same version,
2) I should learn some more about these Express VI things!

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 25 of 26
(969 Views)
You're right!!!
0 Kudos
Message 26 of 26
(940 Views)