Losing track of DLL files

[WMassey]

I'm having problems with LV losing track of the locations of DLL files when I move code back & forth between the development machine and the target machine. The DLL files are located in (what I think to be) the same location on both machines yet whenever I move the code from one machine to the other (direction does not matter) I have to tell LV where to find the DLL files and that always triggers a warning like this:

Virtual Instrument

- The external library expected to be at

"Program Files:\SI Image SGL C\tiff2vi.dll" was loaded from

"C:\Program Files\SI Image SGL C\tiff2vi.dll".

- The external library expected to be at

"Program Files:\SI Image SGL C\SpecInst.dll" was loaded from

"C:\Program Files\SI Image SGL C\SpecInst.dll".

:

When I am called on to identify the path to the DLLs it's by browsing from C: --> Program Files --> SI Image SGL C, yet somewhere along the way LV turns C:\Program Files into Program Files: and remembers it as such.

Any idea what might be causing this and what I might do to prevent it or fix it?

[didierj]

Using DLL in LV I have also seen odd behaviour, especially when the DLL doesn't reside in the search path of the computer. Usually this would mean

- either directory where the app resides

- or windows/system32 (if in win-environment)

Alternatively add your directory to the system-"path" variable. This should give you a workaround.

Didier

[WMassey]

According to Wendy from NI, this would seem to be a "feature" of LabVIEW.

I'll need to try one or more of the workarounds offered here.