cannot resolve confilict in project

[Barionics]

In my project I have a global variable VI. The project is trying to load this VI from a copy of a similar but different project on my hard drive, to my annoyance, so I added a copy of the global to the correct folder and then added this to the Project, so I now have two copied of the global variable listed, and a conflict error.  There is only one conflict, no others. Howcome I cannot resolve this conflict.  Every time I try the rogue VI dissapears from the list only to reappear a few seconds later under dependancies.  Anyone know why or how to fix this?

[RavensFan]

Temporarily rename the folder of the other project.  Then load your new project.  It won't be able to find the other file and will give you a broken VI, or ask you to find the VI to be used.  Fix it so it points to the correct locations and save the VI's.

Once you are done, close your project.  Go back and rename the other project folder back to its original name.  Try reopening your new project again to be sure the conflict no longer exists.

[Barionics]

Sometimes this approach helps, but not always.  I have just completely deleted an old copy of my project folders from my harddrive, to prevent the LV project view from trying to link to them, but I failed.  Annoyingly, sometimes, the project will refuse to let me select an existing copy of a VI, insisting that I chose a copy which does not exist on the drive.   How daft is this?  

[RavensFan]

While I've fought with trying to get conflicts resolved, I've never had things be that extreme before.  If it can't load it because it's been deleted, then it should show up as a missing subVI.  If you can't replace it with the correct subVI, then just delete it, drop the correct one, and reconnect the wires to the subVI's terminals.

[Bob_Schor · Accepted solution]

It shows in Dependencies because you have (at least one) VI in your Project that lists this particular Global as the one to you.  Go into Dependencies, click this Global and ask it to Find Callers.  It will point to one or more existing VIs.  Open those, find the Global, and Replace it with the correct Global that is in your Project.  When you've done all of the Replacements, the Global in Dependencies will vanish and your Conflict will disappear.

Bob "Been There, Done That" Schor

[Barionics]

Hey, I've found the answer to the problem. 

1/ Delete (or hide) the folder which the project is wrongly opening the VI from. 

2/ Right click the VI in dependancies, and select "Why is this VI in dependancies?". This gives a list of VIs for which this is a dependancy.

3/ Individually open each VI in the list.  When it complains and says it can't find the sub-VI, then point it at the right one. Having done this for all the VIs in the list the conflict magically dissapeared. 

[RavensFan · Accepted solution]

Isn't that pretty much what I said?

Okay, I did say "load the project".  But I meant not just the project window, but your main VI as well.  When you load the main VI, it won't find the missing subVI, and it will ask you to point to the correct one then.

[Barionics]

Yes, but I thought it should automatically go and find the right VI. Now I know how to find the calling VIs that makes the difference. Thanks to both of you for your advice, between us we worked it out!