LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

executable searchs for missing DLL

My VI runs normally when done interactively, as I browse the sub-VIs, all the DLL calls are satisfied with the corect DLLs. The compiled version prompts me for an old VI that doesn't exist anymore, what's wrong?
0 Kudos
Message 1 of 2
(2,561 Views)
Is the problem with calling a DLL or with calling a subVI? Where is the DLL located and how are you telling the executable to find it? What role does/did the subVI play? Remember that built executables only look in certain directories for a given function library. For any built executable, be sure to have your DLL installed in one of the following:

1) The same directory as the executable,
2) \windows\system (\winnt\system32 for NT systems)
3) any path that is specified with the "set path" command in the autoexec.bat file or listed in the path environment variable on NT

Eric Sulzer
Applications Engineer
National Instruments
http://www.ni.com/ask
E. Sulzer
Applications Engineer
National Instruments
0 Kudos
Message 2 of 2
(2,561 Views)