How to not allow default values to be submitted

[altenbach · Accepted solution]

Your typedef has inner typedefs that you did not attach. Your code does not link to the attached typedef.

Can you explain why Carrier# is DBL? An integer would probably be more reasonable.

Here's a quick rewrite to give you some ideas. (I don't have your subVIs).

[billko]

Is it possible to prevent this from happening in the first place?  I think usually it is easier to not allow something to happen than to fix it when it does.  You know, make it impossible to enter letters instead of dealing with them when the user enters some.

[altenbach]

---

@billko wrote:

I think usually it is easier to not allow something to happen than to fix it when it does.  You know, make it impossible to enter letters instead of dealing with them when the user enters some.

---

I think the current requirements are to check if the controls are at the defaults or if anything (anything!) has been entered in each.

It would be easy to add a subVI that validates the entries against known good values, but that's beyond the current scope of the question. Ultimately, it must be done, of course.

[paintman]

Thank you! And like I said I'm pretty new to the software/programming, I didn't know my carrier number wasn't set as an integer (or what a DBL was). I went ahead and changed that! When you say I need to verify if the path is valid, what does that mean? 

Also, I didn't even think about just making the title a constant... I appreciate all the advice!

[altenbach]

Once a path is selected or formed you might want to verify that the resulting path is writeable and not malformed, especially if the user entered a path manually. Once you build an installer, the exe will be in a system folder and that might need to be unlocked to allow writing.