Locked out of my files - My only version of LabVIEW suddenly gives error code 9

[AustinP]

---

@crossrulz wrote:

---

@AustinP wrote:

Storing backups in another folder never occurred to me.

---

Please just Google "Software Configuration Control" (SCC).  The general idea is you have a database that holds your code and lets you revert to any previous version you might have had.  You can also add notes saying what you did for the check ins.  Personally, I am a fan of Tortoise SVN for my SCC software.

It looks like Tortoise SVN is already installed on this computer, but nobody was using it. I will look into that immediately and set that up for this project. Thank you. From the name of it, I never would have known that it had SCC.

---

[aputman · Accepted solution]

---

@altenbach wrote:

Opens fine in a newer version and claims to be saved LabVIEW 2016. This means we can recover all this for you and down-save it. Puzzling....

---

Wow...that is crazy.  Are you sure there are no other versions of Labview installed?  

Apparently you have the only up-saving installation of Labview (outside of NI....if there is such a thing, which apparently there is).  

[AustinP]

---

@aputman wrote:

---

@altenbach wrote:

Opens fine in a newer version and claims to be saved LabVIEW 2016. This means we can recover all this for you and down-save it. Puzzling....

---

Wow...that is crazy.  Are you sure there are no other versions of Labview installed?  

Apparently you have the only up-saving installation of Labview (outside of NI....if there is such a thing, which apparently there is).  

---

WOW! This computer does have LabVIEW 2016. I have no idea how Windows skipped around LabVIEW versions since I was just double-clicking to open the files. Anyway, the team will be pleased to know that they have two licenses of LabVIEW. LOL

I missed it because the 2016 version is 64-bit and the 2015 version is 32-bit. Some programs include 32-bit as well as 64-bit. I never read the middle part of the name.

Thank you everyone. And, even though this was simple, I will still start using SCC.

[arteitle]

Correct me if I'm wrong, but doesn't double-clicking on a .vi in Windows cause it to try to open it in whichever version of LabVIEW was last used, rather than the one that created it?

[aputman]

---

@arteitle wrote:

Correct me if I'm wrong, but doesn't double-clicking on a .vi in Windows cause it to try to open it in whichever version of LabVIEW was last used, rather than the one that created it?

---

That is the way it works for me.  2011 and 2012 installed and the last version used opens when double clicking a VI.

[AustinP]

---

@arteitle wrote:

Correct me if I'm wrong, but doesn't double-clicking on a .vi in Windows cause it to try to open it in whichever version of LabVIEW was last used, rather than the one that created it?

---

This seems to be the case. It was opening them with 2016, then. But, it must have switched to 2015 after 2016 crashed.

[crossrulz]

---

@arteitle wrote:

Correct me if I'm wrong, but doesn't double-clicking on a .vi in Windows cause it to try to open it in whichever version of LabVIEW was last used, rather than the one that created it?

---

No correction needed.  That is exactly how it behaves.  So always be care about which version of LabVIEW you are working in.  I have a habit of explicitly opening LabVIEW before attempting to open a VI from Windows.  Helps alleviate the issue most of the time.

[billko]

---

@crossrulz wrote:

---

@arteitle wrote:

Correct me if I'm wrong, but doesn't double-clicking on a .vi in Windows cause it to try to open it in whichever version of LabVIEW was last used, rather than the one that created it?

---

No correction needed.  That is exactly how it behaves.  So always be care about which version of LabVIEW you are working in.  I have a habit of explicitly opening LabVIEW before attempting to open a VI from Windows.  Helps alleviate the issue most of the time.

---

This is how I do it, also.  I have a bunch of different LV versions on my computer, so I never double-click on a LV file.  I'm guessing the OP would never have developed this habit  since it was assumed that there was only one version of LV installed.  😞

[Taggart]

Bill,

         You should try using the Automatic Version Manager (see link below)... It should help.  

http://sine.ni.com/nips/cds/view/p/lang/en/nid/215988

This also goes for anyone else running multiple versions of LabVIEW on the same computer.

Enjoy.

Sam

[GerdW]

Hi Austin,

the last file for LV2015…

edit: failed to read the whole thread…