file dialog error 43 happens for no apparent reason.

[edCubed]

I do like to bitch about labview....

Here's why I'm confused:

On Friday I was able to run this program almost 40 times with no errors using the same initial file path I'm using now that's giving me the errors.

Then error 43 appeared and I couldn't figure out how to fix the program but eventually I cleared the text from the input string controls and the program

worked for the rest of the day. This morning I am getting the same error that appeared on Friday and clearing the fields does not appear to fix the problem.

I seems to me that there must be some bad setting attached to one ore more of the string controls somewhere that's causing the error everytime I run the program. But I don't see where it is.

I'll check the filepath though and make sure it's still correct.

Thanks,

[altenbach · Accepted solution]

---

@edCubed wrote:

I just tried using "limit to single line", "update value while typing", and I tried disabling "enable wrapping". None of these worked.

---

I was wondering how you settings are, I did not make a statement on which setting is better.

"enable wrapping" is a cosmetic property and does not change the underlying data. It does not matter.

"limit to single line" is useful for controls, because the enter key will end the input.

"update value while typing" is also not something you want.

Now back to your error: The control named "Die location" contains a newline character by default (change to \-codes display and you'll se a "\n" (0F in hex). Change that to an empty string, make the new value default, and re-save the VI. Most likely, the \n persists invisibly when you enter the desired text.

(NTFS forbids the use of characters 00-1F, see also here, thus you cannot have that in a file name!)

[edCubed]

I removed the redundant .txt and it didn't fix the error. But then I tried typing in "1" in every string control and it made the error disappear.

Now I'm using the same values in the string controls I used throughout my testing, and everything seems to be fine.

I still have no idea why the error appeared and why typing in 1 in the string controls fixed the problem. My guess is that there is a bad value

that occasionally gets stuck in one of the string controls and generates an error but for some reason I can't see this value...

Anyway thanks for the help, and let me know if you figure out what's actually causing this error. I'll probably be back on the forum when this error

occurs again.

Thanks again,

[edCubed]

Interesting!

sounds like this may be the problem. I'll make sure that there are no hidden end lines in my controls and go from there.

[altenbach]

Yes, make sure all string controls are empty by default and don't contain invisible stuff. You should also make sure that they are set to "limit to single line" (right-click...). This way you cannot accidentally enter a new line when entering values.