Finding missing VIs.

[sumitrishi]

I have my VIs structured in different folders one of them happens to be common . The VIs in this common folder are used by different libraries that I create for my application. Now everytime I copy them(.llb) to a diffrent computer. LabVIEW starts searching for these common VIs . Can I control this programmatically; I mean tell LabVIEW where they are programmatically? Do I need to include these VIs with other files in the library which is a less challenging solution.

[Oleg]

Hi,
may be this is not exactly what you need but you can save your VIs as "development distribution".
To do this open the main VI of your application. Then goto File->Save with options... menu. Choose "development distribution" option and click "Save" button. The dialog will appear where you must specify new directory, or new LLB where the application will be saved. This will save your main VI and all subVIs from different levels and directories in the same LLB. Also the paths will be changed in appropriate way. And this will allow to open and run your application from any other PC.
The only problem could happen if you run some VIs with application server using programmatically sepcified paths.

Good luck.

Oleg Chutko.

[sumitrishi]

Thanks for your suggestion. I think I would defintely have trouble doing this as I m using VI server with programmatically specified paths.I need to look into some other possibility.

[Greg_McKaskle2]

> Thanks for your suggestion. I think I would defintely have trouble
> doing this as I m using VI server with programmatically specified
> paths.I need to look into some other possibility.

One trick that you might be able to use to your advantage is to make up
a dummy VI that has calls the roots of your library. You dynamically
load this dummy VI wherever you want and it magically pulls your subVIs
into memory. You never use the reference to the dummy VI, and you can
now use whatever path you like to load the real library functions, in
fact you can just wire up a string and they will load fine. This works
because LV can only have one VI with a given name in memory, and it
doesn't matter where it comes from.

Greg McKaskle