Power Outage now Labview won't start

[billko]

But you can only save for previous back to 8.0 I believe.  Does this have anything to do with the introduction of projects?

[antique]

I have Labview working again somewhat. I still have some files that are not opening correctly. But working them one at a time. I started to uninstall and reinstall labview and seen the repair button. It repaired the 7.1 and ask for DAQMX 8.1 and it repaired that also. The Program comes up and is having trouble with a few VI's I created. I am able to point them to the correct location or recreate the vi as I did before. Still has a little work to get it all operational. The program does seem to run on 2015 version but I do not have the equipment connected to the PC.  

What would be the proper way to backup when I get it working again? I do not want to do this again in the future and it I can talk them into a new PC I would like to be able to transfer and get it working quickly.

Thank you for all of the suggestions.

Gerald

[RTSLVU]

We do not have any sort of auto backup or source control here, so I am on my own when it comes to backups.

First and foremost keep your project files organized and in one location (Directory)

I have a "code" directory under "My Documents" and it contains sub directories for LV2013, LV2014, and LV2015. Inside each of them is a subdirectory for each project that contains the projects VI's controls and etc plus the .lvprj .lvlps and .aliases for the project.

Every now and then I manually copy the entire "code" directory and all it's subdirectories to a location on my company's network server.

I also copy the user.lib and instr.lib to the network

C:\Program Files (x86)\National Instruments\LabVIEW 2015\instr.lib and C:\Program Files (x86)\National Instruments\LabVIEW 2015\user.lib

Now when I get a new computer I still have to reinstall LabVIEW and any other drivers that need to be installed.

Copy my code directory, instr.lib and user.lib to the new computer and I am running again like nothing happened.

Been doing it this way for over a decade and it has not failed me yet.

[Bob_Schor]

In my experience, LabVIEW is pretty good at handling its own files, including those in vi.lib, instr.lib, and user.lib.  You do, of course, need to remember which toolkits and addons (including external packages) you installed ...

I also follow RTSLVU's scheme of keeping my LabVIEW files organized by Project (and always use LabVIEW Project).  For the most part, my Project's "physical files" (on disk) match the Virtual Files found inside Project.

I am a great believer in keeping my LabVIEW code under Version Control.  I've been using Subversion for at least 7 years, and have not had any regrets (except when I forget to update or commit).  This (in my opinion) is by far the easiest and probably best way to keep my LabVIEW code "safe" and "organized".  I don't often have to go back to earlier revisions, but this feature has saved me a lot of grief on occasion.

Bob Schor