Excluding search path for vi:s

[Peeker]

Hi,

I want to convert a number of llb:s into dir:s, while keeping the llb:s parallel to the dir:s. The reason for this is that files in dir:s would be easier to handl in our version control software (Rational ClearCase), but we want to keep the llb:s in order to keep track of our version history.

Hence, there vill be two copies of the same vi:s i parallel, one in the dir and one in the llb. Is there a way of forcing LabVIEW to load the vi:s from the dir:s, so that we can be sure to get the latest versions?

//Peeker

[RobCole]

Before loading the main VI, rename the .llb and then the VI should look in its own directory first to see if the VIs are there. If it doesn't find them, then it will ask you to find them - any directory that you choose will be the first place that it will look for the next VI. After loading everything successfully, just resave and the default will be the directories and not the .llb. A bit of a pain in a large project, but it does work.

Rob

[Greg_McKaskle2]

> Hence, there vill be two copies of the same vi:s i parallel, one in
> the dir and one in the llb. Is there a way of forcing LabVIEW to load
> the vi:s from the dir:s, so that we can be sure to get the latest
> versions?
>

When loading subVIs, LV first looks in memory, then in the location
specified in the caller, then it uses the search path to try and locate
it. Honestly, most cross-links happen because the VI is already in
memory. In LV7, and possibly in LV6.1, LV will give a warning message
after load saying that a VI was loaded from a location different than
what was expected. When this happens, unload the VIs without saving,
unload the things that were already in memory, then load again. If you
save, then the callers will now expect to fi
nd the callee in the new and
incorrect location.

To get rid of the search path, go to Tools>>Options, on the paths page,
and empty out the search path list. This will be inconvenient if you
ever rearrange things, and you might find that is convenient
since it will represent places that other VIs were found. This means
that if you rename a directory, you can show LV the new location once
during a load, and it will find all of the other VIs that are in the
directory.

Greg McKaskle