LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview 7.1 gives error while loading files

Solved!
Go to solution

Hi all

I am getting VI's missing error when i am open a .vi file .it load about 480 subvi's .the problem i am facing is that while loading it the subvi's

goes missing & when i open that particular subvi then the error message goes away.this is not in particular to a particular subvi.anytime

i open the program the missing vi's list is not the same as of the earlier.since i am going to convert it into a .exe file & if some vi are missing

then it is incorrectable.also mass compile is not happening

 

hoping for quick response

 

Dhiraj Kumar 

0 Kudos
Message 1 of 3
(2,699 Views)
Solution
Accepted by topic author dhiraj03416

Hi,

 

Its not the problem of the VER 7.1, I think you may have changed the location of the SubVI's or modified the name of the VI's. So generally i suggest you to keep all the subvi's under the same location all in the same folder and link to the main VI if you change the name also relink to the main VI and then save. Do this and then create the EXE. 

Regards
Aks

(Appreciate answers by giving KUDOS)
Hit the stars.............. sky is not the limit.
0 Kudos
Message 2 of 3
(2,694 Views)

Hi Dhiraj,

      I agree with akshath that it may be related to a VI location change - I've also seen very long VI names and directory names cause strange problems as there are OS limitations related to total path-lengh.

 

You've probably tried this, but it's important to ask - once you open the Top-Level VI and manually locate all the "missing" VIs have you tried "Save All"?

 

On a seperate topic (unless you're using a formal Source Code Control?), when you compile, you might consider creating a "snapshot" of the soure-tree, by doing a Save-As ("Development Distribution") and creating an LLB.  Create your EXE from the LLB and archive both the LLB and EXE.  This way you can continue developing the source tree, but have the option to return to a specific distribution and create a "branch" on your source tree.

 

Cheers!

 

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 3 of 3
(2,679 Views)