@GerTheDwarf wrote:
I'd like to add that one of the projects I'm working on uses ActiveX, and my projects use different LabVIEW versions but share code (why? because of management red tape), hence my need to compile the whole project before I can build, and my strange questions.
I would assume that you would know that by now, but from your question it looks like you might not - when you save a VI in version X, you can only open it in version X or newer and if you want to use it in an older version, you have to backsave it. That means that your different programs can't share the same VIs and you would need to have different copies for each version.
The best way of doing this without losing your relative paths is by placing the shared code in the LabVIEW\user.lib folder, which is logically linked for each version. Then, you update the shared code in the earliest version and copy the VIs to the user.lib folders of the new versions.
Once you do that, you will have several versions of the shared code, one for each LV version and you will not need to recompile them when building projects.
Another option which is becoming popular is using a virtual machine for each LabVIEW version with its associated drivers, so you don't get conflicts when working with different versions.
___________________
Try to take over the world!
