Is it possible to unlink sub VIs to prevent affecting other projects

[kerryexile]

We are running a validation with different flavours of the same IC which require using the same set of VIs with slightly different settings. In order to avoid confusion for users who are running with one type of silicon we have decided to make a copy of the LabVIEW code in a different area of our project folder on our network. We are concerned that LabVIEW will still find VIs from, say Project A, and use them for Project B, which may or may not cause problems when re-running tests for Project A as some of the VIs may need to be modified for Project B.

We have looked at creating different sub folders and unmapping network drives but are still concerned that LabVIEW will be smart enough to find the Project A files when it should pick up the Project B files. The issue is that we may need to edit some of the VIs for Project B but don't want them to be modified for Project A.

Is there a "One-click" method of unlinking all sub-VIs for Project B and when we load the main VI for Project B we can then manually point to the correct files so that Project A will not be affected and we can still run the VIs for Project A in the same environment with the same network drives mapped?

This is complicated to explain so let me know if you need clarification.

[Phil_]

I don't think there is an automatic way of doing this. (someone else may know better)

I would do a "save as" on the project, duplicate all files elsewhere, then add a prefix to all of your VI filenames.

I tend to do this for projects that re-use old code too. Add a project specific prefix to the VIs and then if I decide to modify things in the new project I don't break old code.

Edit:

Another thought: If it is just settings you want to change rather than the actual code, maybe you could use a config file of some kind to load in the values that are going to change with your different setups. Then you use all the same VIs but just change the config file between different setups.

[kerryexile]

Thanks for that suggestion. I was thinking of copying over the "Project A" files to a removable drive then disconnect the computer from the network and start up the top VI so that it can't find the original VIs and is forced to take the new ones. Then copy that set of VIs to the new "Project B" area and repeat the process.