hide VI search window on startup

[TLE]

I have built an application with the following architecture:

1. Two llb's saved for distribution. These were saved using the "save with options" method so there are a few VI.lib VI's that are in both llb's.

2. One EXE that loads VI's from each llb using the VI server.

The intent is to implement a "plug in" type of architecture. The llb's can be individually updated.

When the EXE is run, the VI search message box pops up until all VI's have been found. I would prefer that this message box is not displayed. I suspect that this is due to there being multiple copies of VI.lib VI's. Is there an INI file setting to accomplish this?

Using LabVIEW 6.1.

Thanks!

[TLE]

Update:

I used the application builder to create exe's for each of the LLB's.  There are VI's in the LLB's that call the "lvanlys.dll" and "lvdaq.dll" dll's.  I specified in the application builder to put these dll's in the same destination directory as the exe's.  Now the "search dialog" is not displayed when the main application is started.

The only difference between the LLB's and the exe's is that I used the application builder and not "save with options".

So it appears the "search dialog" was being displayed as a result of the dll's not being where LabVIEW thought they were.  Building an application must save the appropriate link to any dll's that are used.

Comments?

Thanks!

[xseadog]

The danger of using llb to save and maitain vi can not be over emphasised.
It only leads to heartache.
A corrupt llb destroys every thing.
Safer protocol is to use a windows based architure with folders, thus
if a vi becomes corrupt you still have over 90% of your application functional.

The build will automatically load all files from the windows style architure.
 Your only have to add any dll that are used.

With regard to your two build methods
Building an application that loads llb is not recommened. Corrupt llb means
application will not work!!!
BY building an application from llbs is more apppropiate. Once the build is complete
then it does not matter if llb are lost/destroyed etc.BUT it can cause problems
for next version of application if llb is damaged.

Remember to save bld file so that any modifications can be quickly implimented.

In all cases save project files in zip files etc.
Labview cannot load them  thus less likely to be corrupoted.
In fact suggest you make a zip file each day or failing that each week.
 They can always be deleted after the next version is
proven.

Some actually advice to use source safe,especially if several working on project.
Personally I prefer winzip.

That my 50 ore's worth !!

Chow
xseadog