Message Edited by Nick_F on 08-22-2006 12:03 AM
Solved! Go to Solution.
How exactly do you do this? I am getting the same error message when trying to open a file in my default case, writing to it in the next two cases, and then closing it in the last case. (And I'm having problems closing my AWG, but that's fine).
If you place the attached as a sub-vi, it will provide the folder that the calling vi is stored in. This will work in both the development environment and in an exe.
Is that what you need?
Hehe 🙂 It didn't quite solve my problem, but it solved another problem I've had! I'm not sure how I should have used it to extract the absolute file path and use it further.
I solved the problem with my current structure by using local variables instead of global. I hope that wasn't a bad fix?
Try putting changing the case statement so that the case for 'Run Time System' only has one strip path, and the default case just wires the path straight through without changing it. This should give you the path of the file rather than the folder it is in.
Apologies if this still isn't what you're after... I'm guessing a bit as I can't open your code as I'm on an old version of LabVIEW (8.5)
Here's the simplest way to return the folder directory path of the current VI; just open the snippet up in LabVIEW to view the code.