Stopping Labview when it has to search for a file...?

[Dave M]

When loading opening a new test sequence in labview, the software may go off and search for a dll that may be located in another unexpected directory. Usually, the software will find the file before you can determine which file it was searching for and what path it expected to find the it and where it eventually found it. Is there a way to stop the software load when labview has to search for a file so that the user can easily determine what files may be in an incorrect directory...?

[Joe_H]

if labview is continuosly looking for the same file. Then you need to move that file into the the same directory as your VI by using the library manager. This will stop labview for searching for the same VI everytime. Also when the VI is loading there is an option to stop the loading of your VI and search for the files yourself By hitting the stop button.

[Dave M]

I realize there's a stop button. This button is usually of little help since the search happens so quickly. Also, because of our setup, we can't place the dll in the same directory as the library...

Do you have any other suggestions...?

[RobCole]

One thing that you can do is open the main VI and then do a "Save All". This should save the main VI and all subVIs withthe information of where they loaded the subVIs from. While this doesn't tell you what VIs are in the wrong directories, it should make the loading go much faster since it will not have to look for the VIs.

Rob

[Joe_H]

I do not know what type of setup that you have. But one other thing you can do is. go into the block diagram of you VI that has the .dll right click on the dll go to configure and from there you can tell labview where to load the dll from.Also when the VI is loaded is there any messades the pop up when the VI has completely loaded. saying where these files where expected to be and where they are loaded from.

[Joe_H]

I do not know what type of setup that you have. But one other thing you can do is. go into the block diagram of you VI that has the .dll right click on the dll go to configure and from there you can tell labview where to load the dll from.Also when the VI is loaded is there any messades the pop up when the VI has completely loaded. saying where these files where expected to be and where they are loaded from.

[Dave M]

No, There are no windows that pop up telling me what files where loaded from an unexpected directory. I wish there was. Thanks for your help...

[Evan]

Dave,

If I understand your question you just want the LabVIEW search pop-up to stay up longer. That way the user can see what is being searched for.

One suggestion I have is to add c:\ as the first directory for LabVIEW to search through. You can do this by selecting Tools >> Options >> Paths >> VI Search Path. I have done this and it will REALLY slow down the search.

Let me know if this is not what you where looking for.

Evan
National Instruments

[Greg_McKaskle2]

> One suggestion I have is to add c:\ as the first directory for LabVIEW
> to search through. You can do this by selecting Tools >> Options >>
> Paths >> VI Search Path. I have done this and it will REALLY slow
> down the search.
>

Doing this may have side-effects you don't want. If you have multiple
versions of your VIs/DLLs stored other places on your C: drive, you just
told LV it was OK to load them from there if it finds them first.

To stop the searching, empty the search path. If the VI/DLL isn't in
memory or on disk where it is supposed to be, LV will put up the dialog
asking you to find it and perform no searching on its own. Most likely,
you want to do this once or twice to discover what has been misplaced,
so that it can be re
saved to point to the new location, or relocated to
be where the saved VI wants it, then turn the search path back on. It
gets really annoying and seems lazy when LV always wants you to find
things for it.

One other point is that the initial DLL is something LV is in control of
loading, but once it asks the OS to load a DLL, the dependent DLLs are
something out of LV's control. The OS will do its own searching, but
without a dialog.

Greg McKaskle