"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
info-labview <[EMAIL PROTECTED]>
> Subject: [W] unknown DLLs & executables
>
> Normally, when making an executable, LabView will copy any DLLs that
> the linked subVIs required to a data directory that can reside next
> to the executable. This is fine, thank you NI.
>
>
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.
At 12:52 AM -0500 3/23/04, Michael Aivaliotis wrote:
Andrew,
When building an app, you must specify dynamic VI's with the "add
dynamic VI" button
Andrew,
When building an app, you must specify dynamic VI's with the "add
dynamic VI" button in the application builder. This triggers the app
builder to include any related DLL's or extra VI's... NO?
Michael Aivaliotis
> Now, what happens when your application loads a VI dynamically... and
> i
Normally, when making an executable, LabView will copy any DLLs that
the linked subVIs required to a data directory that can reside next
to the executable. This is fine, thank you NI.
Now, what happens when your application loads a VI dynamically... and
it needs a DLL? The load will fail unless