"Andrew Johnson" <[EMAIL PROTECTED]> wrote: >But if you don't know what will be loaded by your user later on...? I >am working with a situation where users can link in their own VIs >dynamically.
Then I think it is your users responsibility to make sure he gets the entire dependency tree in the right places, sorry! Copying the entire vi.lib is most probably not an option as this is going to violate some copyrights in some ways for sure. Identifying the entire VI dependancy is quite simple. You can save the top level VI with "Save with Options", single prompt, new location, preserve hierarchy, include vi.lib, external subroutines and runtime menus. This leaves out DLLs unfortunately. Another approach may be eventually to use the new programmatic interface to the application builder which I believe is used by the OpenG Application Builder. Rolf Kalbermatter CIT Engineering Nederland BV tel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED]
