cannot resolve conflict in Project

[T_Bragg]

When I open and run the vi as a stand alone vi, it runs and opens without any issue. When I add the vi to a project, I get dozens of conflicts that cannot be resolved. the conflict are from two instrument ".lvlib" files I use for instrument control. I have loaded some sub vi's in the main. When I try to resolve conflicts it might show two locations where the file is found, but has a message indicating the conflict cannot be resolved. Any ideas?

[TMC-NI]

Hi TonyBragg,

That is somewhat odd.  Does it give you any other details on why the conflict is not able to be resolved?

I have a suggestion, I would recreate your project in a different folder, that may resolve the error.  Otherwise, a shorter possible solution may be to recreate your library and/or mass compiling your project folder.

[T_Bragg]

A little more information. I have a talked to an applications engineer as well. The vi, that is causing me problems in the project, can be opened individually from the network drive and I get no erros or conflicts. Only after copying the vi into the project do I see this issue. The problem appears to be caused by device driver vi's ,that are used in the problem vi, from a instrument ".lvlib" file. The .lvlib file originally resided on C: drive but I later moved it to the same network drive as the vi I created. What is happening with the conflicts is it shows two paths for the sub vi's that were used from the .lvlib file. I try to select the network location but both the C: and network locations have a circle with hash mark indicating that the conflict cannot be resolved. When I open the problem vi from within the project it forces me to select a new location for several vi's (I select the network path). The vi can be ran. I save the vi, but still the confilct is there. The reason I have to place this vi in the project is to be able to build an exe. Very furstrating.

[TMC-NI]

Hi Tony,

Have you rebuilt your project and/or your project yet though?  Rebuilding may help in resolving the cross-linking.  Also, you may have already tried some of these steps, but not all of these steps are outlined better than in this article:

Prevent VI Cross-linking with the Enhanced LabVIEW Project

It provides excellent suggestions to resolve the conflicts.  If you still cannot resolve the issue, then perhaps you can post your project and we can take a look at it, it may be some sort of a corruption or a bug.