LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error has occurred when listing the contents of xxx.llb

Hi All,
 
I think I really need help from NI this time ! I was working on an llb and had a great time with that new project when suddenly, no power any more... computer shut down, black screen, and so on...
 
I live in France you know and I assume our power suppliers decided to go on strike just for a couple of milliseconds. Sorry for that, but that library represented a hard work from the past two days and I don't really want to wire the VIs again.
 
Anyway, I am now unable to open my library any more. Could someone help me uncorrupt the vis in it please.
 
A five hundred star rating for the first one who can do it !
Thank you so much by advance,
 
Julien
0 Kudos
Message 1 of 5
(3,418 Views)
I hope someone can help you. To you and all others that read this post, I will reiterate a statement about llbs. NEVER, EVER do development where you are saving your work in an llb unless you have some very periodic backup system. As you've found out, an llb can be easily corrupted by a single VI and that means a lot of work can get lost. Good luck.
0 Kudos
Message 2 of 5
(3,407 Views)
OK, thanks Denis ! That makes me feel better Smiley Very Happy (Just kidding)
 
I remember a post where you said exactly the same thing when someone had to deal with paths : Run-Time System vs Developement System. I said put your VIs in an llb and strike path twice to get the application folder, that will be the same thing wheter you are in a run time system or a development system. I remember you were a bit upset with that...
 
I am sure you are true this time again but this is the first time this happens to me and I usually make copies of my developments. I was beginning a project so that library was the first and unique sample I had.
Even if I am a bit angry with that library today, I think I still prefer to have 5 libraries with a top level VI in each (VI Tree most of the time) instead of 5 subfolders and nothing to recognize the 'top level' VI.
 
Thanks anyway for this answer Denis, you are the greatest wireworker I know and in French I would have said : "I drink your words !" (Literal translation)...
 
Julien
0 Kudos
Message 3 of 5
(3,402 Views)

Hi,

I think you will retrieve some of your VI in this zip file.

Take Denis advice in consideration !!

Regards,

Isabelle
Ingénieur d'applications
National Instruments France
Message 4 of 5
(3,378 Views)

Thanks Isabelle, I'm happy to find my VIs back, I hope you did not have too much hard work to get them out of that llb.

I am still upset with the behavior of those libraries. I would like to keep on using them because I want to trust LabVIEW whatever happens (I mean if I am not the origin of the problem), but obviously libraries are dangerous to use -> Why do they keep on being part of LV functionalities except for compatibility purposes then ??

Thanks a lot,

Julien

0 Kudos
Message 5 of 5
(3,370 Views)