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 > it needs a DLL? The load will fail unless the DLL is nearby... in the > "data" directory. Still not a problem if we know with some certainty > which DLLs might be needed. > > But suppose we do not? In that case, must the entire "resource" > directory contents be moved to "data", in order to support any > possible VI? And if that unknown VI uses/needs vi.lib support, then > should the entire vi.lib directory also be placed next to the > executable? Is this allowed under the LabView EULA? > - Andrew Johnson > - WireWorks West
