LabVIEW 8.20 Project Dependencies Error, cannot resolve path to VIs

[MikiLV]

Hi,

I am developing LV drivers for one of our products. I have migrated from LV7.1 to 8.20. I have decided to use the new project-style approach, but my progress has come to a halt. When I right-click Refresh under Dependencies in the Project Explorer, LabVIEW cannot resolve the path to a number of VIs.  It would appear that LabVIEW insists on trying to load these from the old project LLB file! When I am prompted to find the VI myself, I do so but then an error message is displayed and the problem is not fixed.

I my old project all VIs were created within a LLB library, but judging from the Project-style templates provided in 8.20, NI appears to to have moved away from that, so I decided to extract the VIs from the LLB library and use them singly in the new project. I extracted the VIs from the LLB library from within Windows Explorer and once I copied all VIs to a temp directory, I placed the VIs in the new project under the relevant folder structure I had previously created.

I also re-mapped the palette view using Tools>Advanced>Edit Palette Set, Once I could see all icons in the palette. I added all VIs to the relevant project directories. I have tested a number of VIs and I am confident they work as before.

But when I look at the Dependencies under Project Explorer, and select refresh... LabVIEW cannot find the VIs I have placed in the project folders, It seems to KEEP TRYING to look for the VIs in the old project LLB library path (how can it be!). When I point it to the correct VI in the new folder and press OK, and error message is displayed! Please see screenshots in attached document.

How can I persuade LV that the VIs are no longer part of a library?

I have attached a document with screen shots to help show the exact nature of the problem.

Any help would be greatly appreciated.

Best Regards

Michele Ferraioli

[JB]

Try this :

• Close the project
• Rename the old LLB
• Open the project
  
• Open the main VI
• Ctrl + Shift + Run the main VI
• Save all
• Refresh the dependencies
  

[MikiLV]

I followed your instructions, but It does not seem to have worked. LabVIEW loaded the VI from the LLB I renamed (see attached file)

[JB]

Move the old llb to another directory - even another drive if possible - and try again. LV must be compelled to relink to the new VIs !

[MikiLV]

Thanks for that JB. I did so in my initial Post, but to no avail. I keep getting the same error message (see file attached in my initial post).  I think I have found a way to fix this though! I have lots of VIs in my project (about 120). I have removed them all and started re-introduced them gradually until the dependency problem showed up again.  It turn out that the Example VIs were creating the problem! For all other VIs, LabVIEW was still prompting for each VIs path, but from then on it referenced the VI from the correct path.

With the Examples though, I have had to replace each VI manually (see attachement). When I re-compiled, saved and closed the VI, LabVIEW generated a large number of file i/o error messages. I am not sure, but I think it tried to save to the original LLB, but this time it was forced to admit, it was no longer there!

I have re-introduced the LLB, mass compiled all VIs and tried a few other things to check if the problem would come back, but luckily it didnt

I think I am ok on this now, thank you v. much for your help.

[JB]

I am happy that you went out of the tunnel !