tracing *.vi paths to llb's...?

[Peter Clements]

hi all
i have been given some code which falls over when i try to start tells me
straight away that certain files (vi's) are out of date, but does not tell
me which library they are in, is there a way to find out which vi's belong
in which llb's....?
thanks in advance

[ian_fung]

Will this helps?

Menu > Browse > Show VI Hierarchy

In Hierarchy Window, check the following
Menu > View > Full VI Path in Label

Nouse-over any VI will show its path, telling you it's location.

[ian_fung]

Will this helps?

Menu > Browse > Show VI Hierarchy

In Hierarchy Window, check the following
Menu > View > Full VI Path in Label

Mouse-over any VI will show its path, telling you it's location.

[Peter Clements]

hi
well the whole program does not load fully as there are vi's missing and i
cannot view the hierarchy....
the program is the test executive but there are sequence files that do not
load as i am told that the call back vi is too old for my ver of lab view,
this is all since a crash yesterday, and i have no idea why....
thanks again
pete

"ian.f" wrote in message
news:50650000000500000009AB0000-1031838699000@exchange.ni.com...
> Will this helps?
>
> Menu > Browse > Show VI Hierarchy
>
> In Hierarchy Window, check the following
> Menu > View > Full VI Path in Label
>
> Mouse-over any VI will show its path, telling you it's location.

[ian_fung]

hi there,

I am sorry that I can't help, at least for now.
Hope someone else manage to help.

All the best and
warmest regards
ian

[Peter Clements]

thanks any way

i reloaded the test exec and it seems to work ok now, but i need help in
saving the location of the vi's that i am using within the test exec as it
seems to ask me each time where the vi's and llb's are...

pete


"ian.f" wrote in message
news:5065000000050000004FAB0000-1031838699000@exchange.ni.com...
> hi there,
>
> I am sorry that I can't help, at least for now.
> Hope someone else manage to help.
>
> All the best and
> warmest regards
> ian

[Al_S]

Sounds like you need to do a mass compile, which will update and save all vi's in a directory, whether they're stand-alone .vi files or in llb files.

How to start a mass compile varies with the version. In LabView 6.1, goto Tools >> Advanced >> Mass Compile, then browse to the directory where you want to start. All vi's in the selected directory and its sub-directories will be compiled and saved for the current version. LabView will generate a report if there are vi's that it couldn't automatically update.

[Peter Clements]

thats sounds like what i need! many thanks! 🙂

"Al S" wrote in message
news:50650000000500000054AB0000-1031838699000@exchange.ni.com...
> Sounds like you need to do a mass compile, which will update and save
> all vi's in a directory, whether they're stand-alone .vi files or in
> llb files.
>
> How to start a mass compile varies with the version. In LabView 6.1,
> goto Tools >> Advanced >> Mass Compile, then browse to the directory
> where you want to start. All vi's in the selected directory and its
> sub-directories will be compiled and saved for the current version.
> LabView will generate a report if there are vi's that it couldn't
> automatically update.

[Peter Clements]

just wondering, does this aply to the test exec locating vi's and llb's to
run seq tests also...?

"Al S" wrote in message
news:50650000000500000054AB0000-1031838699000@exchange.ni.com...
> Sounds like you need to do a mass compile, which will update and save
> all vi's in a directory, whether they're stand-alone .vi files or in
> llb files.
>
> How to start a mass compile varies with the version. In LabView 6.1,
> goto Tools >> Advanced >> Mass Compile, then browse to the directory
> where you want to start. All vi's in the selected directory and its
> sub-directories will be compiled and saved for the current version.
> LabView will generate a report if there are vi's that it couldn't
> automatically update.

[Al_S]

I suggested a mass compile because of the error message you received: "the call back vi is too old for my ver of lab view". If the Test Executive can't find some VI's, that may be another problem.

Did your hard disk crash or did Windows just crash?
Did you reinstall your VI's or just the Test Executive?
Are you sure you reinstalled your VI's into their previous directories?
Did you need to reinstall LabView?
Are the VI search paths different now? See the search path in LabView 6.1 at Tools >> Options >> Paths >> VI Search Path.

If LabView can't find a sub VI, it will show you the complete original path to the VI (including the LLB file, if any) while it's searching. After completing an unsuccessful search, a file dialog will open asking yo
u to find the missing VI. In that dialog, it shows only the vi name, not the complete path. But you can move that dialog out of the way to see the complete path in the search dialog behind it.

If you realize that the VI or LLB was moved and you want to restore the original location, you can stop the VI load, exit LabView, move the VI or LLB using Windows Explorer, restart LabView and load your application. If you want to use the new location, browse to the new location to locate the VI when LabView prompts you to find the VI. After the load is complete, exit LabView. It will prompt you to save calling VI's recompiled because sub-VI's were moved. After that save, LabView will find the VI's next time you load your program.