dir.mnu project conflict

[Tim_Butler]

Hello,

   I have a conflict in my LabVIEW project which I can't resolve. When I open a vi in my project I get a "Project Dependency Conflicts Detected" dialog:

   When I close this window the dependency section of the project manager opens:

but the items aren't highlighted with the usual conflict icon and the "reolve conflicts" menu item is greyed out. I previously had an older version of the Pacific power library installed, but I've removed that from my instr.lib folder. Does anyone have any idea how to resolve this?

   Thanks in advance,

        Tim 

[david.bolt]

Dear Tim

The reason this is occuring is the instrument driver you uninstalled; Pacific Power UPC Series, was previously located where all instrument drivers reside; in the instr.lib folder. Having deleting/removing this, VIs in your project still require these dependencies which no longer exist.

Have you tried reinstalling the driver? If this fails, I suggest mass compiling the project. Please see steps below:

1. From the project, open the VI or VIs that call the instrument driver. LabVIEW will look for the driver VIs in instr.lib, which no longer exists.
2. Choose "Browse" and navigate to your driver library on the shared drive. This added my driver library as a dependency to the project.
3. Save and close the VI.
4. From the project, go to Tools >> Advanced >> Mass Compile...
5. Navigate to the folder containing your .lvlib file and select "Current Folder."
6. Mass Compile.
7. Save the project and close it.

[Tim_Butler]

Hello David,

   Thanks a lot for your response. I haven't re-installed the old driver, as I'd like to continue using the updated one. I've tried the mass compile option that you suggested, but I missed out the first three steps as there are no VIs which call the .mnu items. I'm afraid the mass compile hasn't solved the issue. I can send the log to you if you would like, is there anything else you can suggest that I try?

   Cheers,

    Tim

[Timothy_Wright]

In case you're still having the same problem, I think this list of known issues (namely issue 188425) may have something to do with it.  I am having the same problem, but haven't tried installing LV2009 SP1 yet to fix the issue (I'm not upgrading to LV2010 just yet for this project).

http://zone.ni.com/devzone/cda/tut/p/id/11869#188425_by_Category

-Tim