Could there be independent VI paths for different versions of LabVIEW?

[mcsynth]

Hello, When jumping between different versions of LabVIEW (6.1, 7.1, 8.5) it is annoying that the current path for one becomes the current path for the other.  If I am working with LV 7.1 in a folder dedicated to 7.1 VI's, and then open LV 8.5, I don't want 8.5 to go to that 7.1 folder by default.  Alternately. if I was working in LV 8.5, closed it out, and then I click on a 7.1 VI, I don't want it to open in LV 8.5.  I've tried changing the path options in each version of LabVIEW, but that doesn't seem to help.  Is there any way of isolating these folder paths from one another?  One of our newer LV guys accidently opened some 7.1 code in 8.5.1 and then saved it.  Luckily, I had archived code to return to, but it could have been a disaster.Thanks for any ideas,McSynth

[smercurio_fc]

You're actually asking two different questions. The first question has to do with which version of LabVIEW gets launched when you double-click a file. This is an operating system thing. The one that gets launched is the last one that got used. (Your first question will be: can this be changed? Answer: Change the operating system. Or, play around with the registry each time you quit out LabVIEW.) The second question has to do with search paths. These are independent. However, a VI will contain information about its subVIs in terms of where to find them. This is not a function of LabVIEW, as it is a function of the VI. Thus, it will make no difference which version of LabVIEW you use to open the VI. You can, if you wish, modify the search paths that LabVIEW uses to find VIs for each version of LabVIEW from the Tools->Options menu. However, this will not eliminate the problem, and your best bet is to keep those backups frequent.