How to tell LabVIEW where to find sub-vi's

[Jeff in Pleasanton]

I tried to open a hierarchical vi this morning with my development pc off the network.  I got an error message telling me that NI 9211_TC.vi was not a valid vi.  The NI 9211_TC.vi is embedded in a library file that is physically located in the same folder as the top level vi I was trying to load.  I think the top level vi wanted to get NI 9211_TC.vi from our server, but I was off the network, so LabVIEW got confused.

I was never given the chance to browse for NI 9211_TC.vi when the top level vi was loading.

Once the top level vi was loaded (with a broken run arrow because of the missing sub-vi), I could not find a tool to let me replace the "question mark" sub-vi icon with NI 9211_TC.vi.

I tried double-clicking the library file containing NI 9211_TC.vi (in the Windows Explorer window), but that invariably caused WIndows Explorer to crash (is that a bug?).

So... how do I get LabVIEW to find a vi that lives in a library file in the same directory as the top level vi?

[tbd]

Hi Jeff,

> I tried double-clicking the library file containing NI 9211_TC.vi (in the Windows Explorer window), but that invariably caused WIndows Explorer to crash (is that a bug?)

Probably! - but where - in Windows or LabVIEW?

If it's any consolation, I've been seeing Exploere hang, lately, when opening LLBs where LabVIEW was already running.  I'm curious, what version of LabVIEW?  Do you have "Windows Explorer enabled for LLB files"?

I expect you're already past the problem you posted, if not...

Try closing/opening LabVIEW, then, within LabVIEW, browsing to and opening the 9211_TC.vi.  With 9211_TC.vi  opened, launch the top-level VI.  You may see a warning about files expected to be in one place, loaded from another.  I'd give that list a once-over for general principles.

Cheers.

[wha@atmel]

Hi Jeff,

if your problem still exists - herewith some remarks.  If you have sub.vi's ( not found with question marks ) you can right click on it

and you will get the chance to "replace" - from Functions Palette you can choose "select a vi"

Other possibility:  

You can organize the "vi search path" ( see pic. attached ) like I do it in a non-standard-LabVIEW- Installation, where the whole user.lib ; instr.lib  and all my projects are located on a server.  The last * in    .....user.lib\*    means  "search in all the sub-Folders" of this user.lib.   This is helpful, if you need to have access to libraries from several PC's in a Lab or whatever.

Hope this helps.

Regards

Werner

[Jeff in Pleasanton]

Many thanks to both of you!  I will add your suggestions to my bag of tricks.

I'm running 8.0.1 and Explorer has been enabled for LLB files since my first LabVIEW install.

Sorry for being trite, but This Forum Rocks.