09-14-2017 02:59 AM
09-14-2017 03:11 AM
09-14-2017 03:30 AM
Thank you for your reply. what is "SCC". Would you mind explaining me more about how to do it?
Regards.
09-14-2017 03:37 AM - edited 09-14-2017 03:40 AM
Hi hadibashiri,
SCC means source code control. It's software to keep a history of your source code and should be used for any software development!
As you don't even know about SCC tools you should pick a backup of your source code and get a copy of your LLB.
You made regular backups, did you?
Btw. LLBs aren't recommended anymore by NI for exactly the reason you discovered now: by a small error in the LLB file you lost all VIs in the LLB…
09-14-2017 03:39 AM
You do have a way to make backups? Pull out a copy from one of your backups.
Regards, Jens
09-14-2017 03:39 AM
@hadibashiri wrote:
Thank you for your reply. what is "SCC".
A tool for source code control like e.g. subversion. Such a tool provides an implicit backup of your code. So for your case: use your backup files. If you don't have a backup, well... you have learned a lesson.
Best regards
09-14-2017 03:45 AM
This llb is the only thing i have. Inside it "screw sorting2" is the last vi. All next backup files are inside the corrupted llb.
Regards.
09-14-2017 03:46 AM
well... you have learned a lesson
And for the future I recommend to stop using LLBs. This file format is old-fashoned and not necessary anymore. It was nice in former times when Windows did not allow file names with more than 8 characters. But nowadays it just increases the risk that you loose all your code instead perhaps one vi if there's any corruption within the file.
Regards, Jens
09-14-2017 03:55 AM - edited 09-14-2017 03:56 AM
This llb is the only thing i have. Inside it "screw sorting2" is the last vi. All next backup files are inside the corrupted llb.
Then you'll probably have to redo your work, starting from that point... ![]()
Regards, Jens
09-14-2017 04:08 AM
It's a great failure for me, But thank all for replying. Failure is an experience.