Why, when I try to load a specific VI that I've edited and saved numerous times, is Labview now refusing to load it?

[philmosk]

While attempting to load, Labview 7.0 requests the location of the VI with the same name, and all attempts to point it in the right direction fail: the request simply repeats. Is the VI corrupted? If so, is there any way to salvage the file?

[EdDickens]

I've seen a few others asking about this same problem with LabVIEW 7 lately. As far as I've been able to figure, the VI has been corrupted. It acts like it's searching for a sub-vi with the same name as the top level VI, which you cannot do. The other posts I've read about this have not found a solution. I think you're stuck rebuilding it from scratch.

I think this may be an emerging bug in LabVIEW 7.

Ed

[rolfk]

Ed Dickens wrote:

> I think this may be an emerging bug in LabVIEW 7.

Maybe the way it appears, but corrupt VIs isn't a new thing. It happens
rarely, in fact I never had one since the days of LabVIEW 3.x which I
couldn't trace to some operation external to LabVIEW, but it can happen.
LabVIEW's binary file format is a little bit more suspectible to file
corruption than text format files. A bad HD, memory or a system DLL gone
avry can destroy alot of work if you don't have a good backup strategy.

Rolf Kalbermatter

[PJM_Labview]

Hi Philmosk,

May be you could try to open the VI by reference and see what happen. If it does work (I am not very optimistic there), use the save method or save for previous to save your VI under another name.

Good luck

PJM