ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Works until I save it.

Works until I save it. Then when I reopen I get a number of sub-VI are either missing or not executable. All of these are express VI's. Installing 8.0.1 didn't help. Hasn't anyone else seen this? The sub-VI's are not executable because they are missing certain functions that always come from the Express palette. If I replace the sub-vi with another copy and then put the original one back (without changing it), the error goes away. But this happens every time I open the main program.
0 Kudos
Message 1 of 4
(2,905 Views)
Could you post an example?

Have you changed (even inadvertantly) any of the subVIs that the Express VIs use?

Is it limited to a particular Express VI?  If so, which?

Thanks,
Bob Young

0 Kudos
Message 2 of 4
(2,903 Views)
There is a recurring set of VI's that keep showing up but it isn't always the same one. For example, a VI we wrote called "Write" which writes data to a file uses a number of instances of the Express function called Convert to Dynamic Data. When I bring up the main calling VI, even though it had no erros when I saved it, it is broken because the sub-VI "Write is not executable. And when I look at the "Write" Block DIagram, several of the Convert to Dynamic Data functions have been replaced by boxes with question marks. The context help says "Instance 11 22Saved "Write_June_8_1.vi was not found. I can fix this by wiring in new functions and the program will run as designed. But the next time I close it and reopen it, without even shutting doen LabVIEW, it will give me a similar error for sone others functions in either the main program or one of 2 or 3 other sub-vi's.
Other Express VI's I've seen this happen with include  File Dialog and Time Dealy.
0 Kudos
Message 3 of 4
(2,883 Views)
There is an option to recompile every VI within a main VI, I *think* you have to click the run arrow while holding the CTRL button, this would force LabVIEW to save these express VI's. I have seen this with the file dialog VI.

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 4 of 4
(2,874 Views)