SubVI's " Read Delimited File" can not find file

[LLVV]

Hi, it's for certain that the "Read Delimited File"  part is not dependent on other procedures of the code since it is not coded to be dependent on other procedures of the code and it's only used once in the entire code and the error occurs from built in function itself. 

And yes, VI(s) have been debugged and only has this "File Not Found" issue left to be solved.

Local variable of the variable "File" is just a copy of itself and is not passed from any other variable or procedure.

Plus, "massive" doesn't mean code is problematic, let's not emphasize on the poor wording, I should have said "To save some time to locate the problem from leafing through frames after frames, here is the portion I have trouble with"  

[GerdW]

Hi LLVV,

And yes, VI(s) have been debugged and only has this "File Not Found" issue left to be solved.

Which doesn't answer my question on the value of that local variable named "File"…

Did you used a probe to check its value?

(Another option: use a OneButtonDialog to display the value of the variable before calling the ReadDelimitedFile function. Same as a probe, but also works nicely in an executable.)

Does the file exist in the very same place as is read from your "File" local variable?

[Bob_Schor]

This problem sounds really weird, but here's something to try (provided you can edit the sub-VI that is throwing the error:

1. Look for the file on the PC where the failure occurs.  Write down its path.
2. Open the sub-VI.  Replace the Local Variable holding the file name with a File Constant that you point at the data file.  (Incidentally, did you try to open the CSV file by double-clicking it, and did it open OK?).
3. If you still get a failure, run sub-VI by itself, with the CSV file as its input.
4. If it still fails, it may be time to uninstall/reinstall LabVIEW (but let us know what you find -- someone might say "Aha!").

Bob Schor

[LLVV]

Hi GerdW,

"Did you used a probe to check its value?"

Yes, I probed the local variable "File", its value is same as I typed in the variable "File" (which just a path control that I set the string as its default value, theoretically it's just a constant therefore), C:\Folder-a\Folder-b\Folder-c\file.csv  ( and apparently I am putting generic folder names here, but you got the idea). 

"Does the file exist in the very same place as is read from your "File" local variable?"

Yes, it does, same drive, C: in this case, same folders, same file name, run as administrator, and spell check is also done.  Even computer and labview were restarted a few times, error 7 still pops.

I might have to try a few more things (not sure what yet, but will see) to give more feedback to you guys. 

[LLVV]

Thanks Bob Schor,

I'll try a few more things (not sure what yet, but will see) to give more feedback to you guys later. 

[billko]

My post has been rendered irrelevant by previous posts.

[paul_cardinale]

I use this a lot.  Put it in the error flow after the Read.  Wire in the path you tried to read.  When the error shows up, it will show you the file path it was looking for.