08-18-2009 07:54 AM
08-18-2009 07:57 AM
08-18-2009 08:12 AM
This logic may work for the simple projects, but will be painful for medium - large complicated projects.
VIs created in latest version cannot be opened in previous version directly. You should save these VIs for the previous version as mentioned above. Otherwise, not all code can be saved for the previous version easily (if you will use some features which not supported in previous version)
I would like to recommend stay with LabVIEW 8.6 if it impossible to upgrade department in India to the latest version.
Andrey.
08-18-2009 08:42 AM
Thanks. I will need to convert my code to 8.x. The concern is about code sharing between tow departments.
So what if I save my code in 2009 but not using any new features which not in 8.6, could the other collegue open my code in 8.6?
08-18-2009 08:50 AM
lvfanqie wrote:Thanks. I will need to convert my code to 8.x. The concern is about code sharing between tow departments.
So what if I save my code in 2009 but not using any new features which not in 8.6, could the other collegue open my code in 8.6?
Yes and no. I mean then technically yes, but personally I've got lot of troubles in the past when some VIs (mostly where Vision SubVIs and controls was used) was broken after downgrade from 8.x to 7.x, or just caused LabVIEW crash by opening.
Andrey.
08-18-2009 09:01 AM
lvfanqie wrote:
So what if I save my code in 2009 but not using any new features which not in 8.6, could the other collegue open my code in 8.6?
If you save it in LV 2009, your colleague CANNOT open that code in his/her LV 8.6.
But the converse is true.
Also, since you are using LV 7.1 still, I strongly suggest you to have LV 8.0 also in your system, because that is the only version in in LV 8.X series that will help you to convert code back to LV 7.1.
08-18-2009 09:22 AM
Thanks a lot, guys. I really need to think about to change my quotation to Labview8.6 but not the latest.
LV upgrade compatibility is really an issue when each time we do the upgrading.