Dependancy not found but Build Application works?

[SeanDonner]

I have a pretty complex 8.2 Project that includes a target for MyComputer and a Real-Time PXI target with two FPGA targets under that.  I noticed that if I right click on one of the FPGA target's Dependancy nodes in the project file and go to "Refresh" that LabVIEW will spin its wheels searching for a VI that I no longer use or have on disk.  This FPGA target only contains one VI and that VI loads up just fine.  Where is LabVIEW getting this dependancy information and why does it think its necessary if the only VI I have under that target does not use it?  Also, right clicking on the missing dependancy and clicking "remove" does not seem to do anything.  And by that I mean if I save the project and re-open it, the missing dependancy will still come up when I refresh the dependancy node.

This same problem exists on my "MyComputer" target, unfortunatly that target has over 100 VI's.  Without opening up each and every one of those VI's (and I'm not so sure that would give me any clues based upon the FPGA target noted above) is there some way to see what VI is causing that dependancy?

Thanks

Edit:  I lied, I found a deeply nested folder in the FPGA  target that one of our programmers stuffed some debug VI's into. I'm sure one of these is the culprit.  However, it would still be nice to know a faster way than opening up all the VI's for the MyComputer target case.

Message Edited by SiegeX on 12-16-2008 06:55 PM

[Hillman]

Hi SiegeX,

Thanks for the post and I hope your well today.

"When labview spins its wheels" does the search VI box appear? What can happen is that a VI had certian dependancies on subVIs. Some of those dependancies get changed during development. When this occurs, the project doesn't update to reflect this. Is this the case?

Remember if you include a library but your application isn't calling all of the VIs, you still have to include a complete library. Otherwise it will try to search for the missing VIs (but still work!).

Reading your edit, was your last question, How can you quickly locate the location of the dependancy on the hard-disk? Or where its located in the Project Explorer?

Thanks again for the post,