How do I restrict a llb to only use local vi's

[paulplasma]

Whenever an .llb can't find a .vi it scours the hardrive and local network looking for it and I really need to stop this. I need to restrict the .llb to only use .vi's that are contained in the .llb (except for system .vi's of course)

[Mark_Yedinak]

The only way you can really do this would be to make sure that the VIs it is looking for are in the llb. I would also suggest that you convert your llb into a lvlib. the lvlib like the project does a better job managing cross linking issues.

[paulplasma]

Many times it is unknown that the vi is missing until you run it and BAM off goes Labview scouring for it.

I read that .lvlib will do the trick but I dont have the time to convert my .llb's at the moment.

I was hoping for a checkbox somewhere.

[Dennis_Knutson]

Take the little bit of time. An llb is obsolete and you should not have used one in the first place. Searching for a missing VI is intended behavior and if you did not create the llb correctly, you cannot stop the search.

[paulplasma]

You may consider .llb obsolete but these .llb's have been around for years with thousands of hours behind them. And they were not built wrong, this happens when someone accidently deletes a .vi from the .llb or someone uses the insanely confusing 'Save As' menu. Either way there should be a check box to restrict non system .vi's to be local to an .llb this way if a problem occurs it can be fixed correctly instead of using one named the same in some completely different project.

[Mark_Yedinak]

I would consider converting the llb to a lvlib. Someone with more scripting knowledge would probably be able to help with a VI to do this automatically. With an lvlib you would get the protects you are looking for. In addition you would know if something was deleted.

[smercurio_fc]

You should also keep in mind that with LLBs, if one VI in the LLB gets corrupted, the entire LLB is corrupted. That doesn't happen with project libraries. Something to consider when trying to protect those "thousands of hours".

---

@paulplasma wrote:

Whenever an .llb can't find a .vi it scours the hardrive and local network looking for it and I really need to stop this. I need to restrict the .llb to only use .vi's that are contained in the .llb (except for system .vi's of course)

---

You can configure the search paths for LabVIEW to use when looking for new VIs. This will limit where LabVIEW looks for missing VIs. This is documented in the LabVIEW Help.

[Dennis_Knutson]

And on the subject of protection, an lvlib is compatible with source code control. As I'm sure you are aware, an llb is not.