LVlib conflict

[craige]

I have a LabVIEW project X that seems to want to load a dependancy from another totally unrelated project Y. See the attached screenshot.

Not sure why LabVIEW wants to load NI_LVConfig.lib from an unrelated RT EXE that was created some months ago. Main.Vi isn't even a real-time VI. Any idea on what's going on here and how to stop this dialog from showing up?

Thanks,

Craig

[Tanya_V]

Hi Craig,

It seems like you have a very large project. It could be that one of your VIs uses a subVI from this other project. Did you change anything in your project before this error started showing up?

Have a great day!

[aeastet · Accepted solution]

This is somethig I learned a long time ago using LLB files. You will have vi's that cross talk. You need to manage them and be very careful that you make seperate copies of a vi if you need something different. If you do not make a local copy and remove it from all of your LLB files. Using a library is good and bad all at the same time. Kinda like Locals. the library file with look the last place the you opened the file with the same name.

[craige]

Thinking back on how this problem may have occurred....

I had project Y open a few weeks ago. This project had code for Windows and CRIO. Often times I drag VIs from my CRIO to my Windows target to test the code when I don't have hardware to deploy too. My thought is that at some point LabVIEW asked me to "Save All" which in some way went all the way down into the NI_LVConfig.lib and reassociated my Window VIs with this RT code.

I guess the lesson here is like you said. Be careful how you manage code.