installing newer version of labview updated all my old code

[Bob_Schor]

This should work (but the operative word here is "work" -- more work on your part will be necessary to keep this from happening again!  Before even starting, set up a Version Control System (the two that seem relatively popular with LabVIEW Developers are Subversion, which I use, and GIT, which a number of my more talented colleagues use.  

First, I recommend that you create Folders for your Projects -- put all of the Projects that you know (and can open safely in LabVIEW xx) in a "LabVIEW xx Projects" folder.  This, of course, assumes that you have a few that haven't been "elevated" already.

Now open a Project that you want to "Revert to earlier version of LabVIEW".  Once the Project is open, you want to do a "Save for Previous Version".  For large Projects, this can be messy and cumbersome.  It has been a while since I've made this mistake, so I can't remember if it does all the VIs in your Project, or only those VIs that are in memory at the time of saving.  If the latter, you'll need to "Save for Previous" for them, as well ...

Bob Schor

[jgvarner57]

---

@Bob_Schor wrote:

This should work (but the operative word here is "work" -- more work on your part will be necessary to keep this from happening again!  Before even starting, set up a Version Control System (the two that seem relatively popular with LabVIEW Developers are Subversion, which I use, and GIT, which a number of my more talented colleagues use.  

First, I recommend that you create Folders for your Projects -- put all of the Projects that you know (and can open safely in LabVIEW xx) in a "LabVIEW xx Projects" folder.  This, of course, assumes that you have a few that haven't been "elevated" already.

Now open a Project that you want to "Revert to earlier version of LabVIEW".  Once the Project is open, you want to do a "Save for Previous Version".  For large Projects, this can be messy and cumbersome.  It has been a while since I've made this mistake, so I can't remember if it does all the VIs in your Project, or only those VIs that are in memory at the time of saving.  If the latter, you'll need to "Save for Previous" for them, as well ...

Bob Schor

---

All Hail Ser Bob!

I use TortoiseSVN, and no one in the group I recently took control of did any of this revision control. Unfortunately, I was in the process of creating these repositories when this little incident occurred, thus screwing up the repositories. That's what I get for trying to be proactive.

I remember earlier versions of LabVIEW only allowing you to 'retrograde' VIs to no more than 5 prior versions, and I am going from 2019 to 2013. I'll give that a shot and see how far it lets me go back, even if I also have to install LabVIEW 2016 as well.

All I noticed when it did the inadvertent update was that it wanted me to change the 'write to delimited file' to the newer version. I can change those back during the retrograde. Hopefully I can fix this and actually set up the repositories effectively.

I'll also make sure each project folder has its own Agilent driver library in its folder, no sharing with the other folders.

[paul_cardinale]

---

@Bob_Schor wrote:

This should work (but the operative word here is "work" -- more work on your part will be necessary to keep this from happening again!  Before even starting, set up a Version Control System (the two that seem relatively popular with LabVIEW Developers are Subversion, which I use, and GIT, which a number of my more talented colleagues use.  

First, I recommend that you create Folders for your Projects -- put all of the Projects that you know (and can open safely in LabVIEW xx) in a "LabVIEW xx Projects" folder.  This, of course, assumes that you have a few that haven't been "elevated" already.

Now open a Project that you want to "Revert to earlier version of LabVIEW".  Once the Project is open, you want to do a "Save for Previous Version".  For large Projects, this can be messy and cumbersome.  It has been a while since I've made this mistake, so I can't remember if it does all the VIs in your Project, or only those VIs that are in memory at the time of saving.  If the latter, you'll need to "Save for Previous" for them, as well ...

Bob Schor

---

I don't like the way that puts a copy in a new place.  I always run my own script that resaves stuff in place.

[paul_cardinale]

Try this

[jgvarner57]

---

@paul_cardinale wrote:

Try this

---

LabVIEW 2019 let me retrograde the project to 2013 (I could have gone all the way back to 2008, wow). I already assembled all the items in the C and D directories to a single 2013 project retrograde folder. I also put a 2008 version of the Agilent driver llb in that folder.

But I am now realizing it also uses DAQmx items as well. Hopefully I can install a DAQmx 2013 as well as DAQmx 2019 so I don't have the same issue. Conceivably it would install the DAQmx drivers in the appropriate LabVIEW 2013 or 2019 Program Files directories, so they don't link to each other either.

Crossing fingers ...

[santo_13]

---

@jgvarner57 wrote:

---

@paul_cardinale wrote:

Try this

---

LabVIEW 2019 let me retrograde the project to 2013 (I could have gone all the way back to 2008, wow). I already assembled all the items in the C and D directories to a single 2013 project retrograde folder. I also put a 2008 version of the Agilent driver llb in that folder.

But I am now realizing it also uses DAQmx items as well. Hopefully I can install a DAQmx 2013 as well as DAQmx 2019 so I don't have the same issue. Conceivably it would install the DAQmx drivers in the appropriate LabVIEW 2013 or 2019 Program Files directories, so they don't link to each other either.

Crossing fingers ...

---

Oh actually, no, NI device drivers you can install only one version and that version installs API into all supported LabVIEW versions.