LV file corrupt? I try to load, it asks to find the file I just tried to load

[Blankman]

I have a LV file that when I go to open it, it brings up the prompt saying "please find the Vi named "xxxx.vi" " which is the file that I just tried to open.  I select the file again and just stays in a loop and never actually opens the file.  Both Ignore Subvi and Stop resort to it going back to the main start screen.   The VI was working fine for sometime, then next thing you know it won't open.  I have a lot of time invested in this VI, please help!

[mikeporter]

Sorry to be the bearer of bad news, but you are (to use the fancy computer science term) -- hosed . If you have a backup of the file, now is the time to haul it out. If you don't have a backup...

One small consolation is that in my experience when I have lost VIs like that I always rebuilt it better than I built it the first time. Besides, you still have all the subVIs it called, so you are at least that far ahead.

Mike...

[X-man]

I have experienced same and agree with above post that in all liklihood you will not see that vi again. One thing to watch out for is crashes during developing which can corrupt files. After losing a few days work once, I decided to each day zip up my entire project (70 MB zipped typically) and then to archive it (I did not want to invest time in learning how to use project managers and I am the only one working on my project anyway). Disk space is nowadays to all intents and puposes free. If I decide on a major structural change during the day, I will zip the entire project there and then and can with comfort make hideously drastic chages without worrying. Of course I always make 2 backups...

[tst]

---

@X-man wrote:
Of course I always make 2 backups...

---

And just in case it wasn't clear enough - some of the backups (CDs are not a particularly reliable medium) should not be on the same computer, and preferably not even in the same building. Lost data can also be caused by fires\power surges\thefts\crashing meteors\alien attacks and so on...

[X-man]

Absolutely tst!

One more benefit of zipping a project, you can ensure labview does not find copies of old vi's...

[xseadog]

Hi Blakeman
Have you tried to load the vi  as a sub vi  on a new vi ?
If you suceed loading  the vi then open front panel and save vi to new location. Do not save to original llb

Hope it works

Chow
xseadog

[mikeporter]

Seadog's post reminded me of something else important: Never store important code in LLBs! Libraries are good for sharing code or building executables, but that's all... You trash one file in the library and all the files are gone. Plus they severely and negatively impact your efficiency during development and make any sort of meaningful source control impossible.

Mike..