05-14-2009 11:52 AM
05-15-2009 12:33 PM
Brian
Always be careful with file paths when calling external files from an executable. If your file paths are static make sure the directory they are pointing to is the same since the executable is likely in another folder than your development VI. You may try to make the paths relative to the runtime folder. While you are trying to debug this try setting the path to a front panel control so you can point to the dll at run time in the executable. Let me know if this helps.
Are you running the executable on the same development machine?
What Version of LV are you using
Thanks
05-15-2009 01:15 PM
Do you have any file operations?
One common culprit is, as Huter said, is file paths, and failure to heed errors from file-related functions.
How are you specifying the path to the DLL?
If you're on Vista, be aware that you cannot write a file in the same folder as your application (if you install in the usual PROGRAM FILES place).
Blog for (mostly LabVIEW) programmers: Tips And Tricks
05-15-2009 01:41 PM
Steve-
I do have file operations, but they are triggered by user input. The crash happen right away, which coincides with the dll calls. I only specify the dll path in the "Call Library Function" popup during development. This is on an XP system.
Thanks,
Brian
05-15-2009 01:52 PM
The crash happen right away, which coincides with the dll calls. I only specify the dll path in the "Call Library Function" popup during development.
Just for grins, pop up a dialog just before the DLL call that says "CALLING DLL", and one right after, saying "BACK FROM DLL"
If you get one dialog, and then the crash, then you're right.
I meant what path are you specifying? is it absolute, or relative?
Blog for (mostly LabVIEW) programmers: Tips And Tricks