How to ignore the errors that occours during the execution of the .vi

[Gquadro]

Hi guys, 

i would like to know if there is a way to igrore the errors that occours during the reading of a txt file because i have to be always in front of my pc to click on "continue".

I have already verified that this is not a problem for the result 

[GerdW]

Hi Gquadro,

---

@Gquadro wrote:

Hi guys, 

i would like to know if there is a way to igrore the errors that occours during the reading of a txt file because i have to be always in front of my pc to click on "continue".

I have already verified that this is not a problem for the result 

---

Implement some programmatic error handling in your code to handle those errors automatically.

(Only when you don't do any error handling LabVIEW will show those error dialogs…)

[RTSLVU]

That is exactly what the Clear Errors.vi is for.

[cbutcher]

You may also find the settings in VI Properties useful:

This can be opened via Ctrl+i or File > VI Properties... (then the "Execution" tab).

[altenbach]

---

@Gquadro wrote:

Hi guys, 

i would like to know if there is a way to igrore the errors that occours during the reading of a txt file because i have to be always in front of my pc to click on "continue".

---

You got some good answers already, but to give more specific advice you need to show us how you are reading the txt file, because there are many (many!) possibilities and the solution depends on the details:

• Express VIs
• read delimited spreadsheet (newer version of LabVIEW)
• Read from spreadsheet file (obsolete) 
• lower level file IO

Who wrote your program and do you have the source code available?

What kind of errors are you encountering (automatic error popup? custom dialog? Specific error? malformed data?)

What causes the error? (file got deleted, file is already open in another application, somebody pulled the SD card? network down and file is on server, etc.)

(Note that if the error occurs deep inside the obsolete "read from spreadsheet file", you cannot suppress the error popup without modifying the system VI, so upgrade or write your own instead!)

Typically it is better to try to eliminate the cause of the error than just to ignore an error popup.. then handle it with code as required if it still occurs.

---

@Gquadro wrote:

I have already verified that this is not a problem for the result 

---

How did you verify that?