How to ensure a user completes all fields required before moving to the next case

[jamie310382]

Can anyone help with this. On my front panel I have 9 string user inputs which must be entered manually. There is a push button which passes these inputs to another VI in the next case structure. When the button is pushed, the VI in the next case opens up. I want to stop the user from accessing the next case unless all fields have benn completed. How do I go about this?

[tst]

Check wether the fields have valid input and if not, disable the "Next" button (by wiring 2 into its Disabled property). You can check that the strings are not empty by using the Empty Path\String...? primitive in the comparison palette.

To do this, I would suggest registering the value change event for all the controls and running the validation code whenever one of them changes. That way, the user will only be able to press the button when all the inputs are valid.

To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here, here, here, here and here are a few you can start with and here are some tutorial videos. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).

[jamie310382]

Thank you. The inputs will always be valid as they are a series of drop down menus.

[JB]

In this case, add an extra, unused entry in each drop down menus and select it by default through the software. Doing so, it will become very easy to check if all selections have been done by the user. The prize to pay is that all the settings must done again every time the screen is displayed.

Message Edité par JB le 06-08-2007 06:27 PM

[Tom.]

Hi,

Take a look at this example, it's quite a simple way to approach your issue.

Cheers

Tom
NIUK

[jamie310382]

Thanks Tom,

Unfortunately I am only running Labview 7.1. Can you save it as a 7.1 and resend please. Thanks again.

[Tom.]

Hi,

The example written in LabVIEW 7.1 is attached.

Good Luck!

Tom
NIUK

[tst]

If the inputs are always valid, what's the point of forcing the user to change them? At least some of them could be OK in their current values.

If you still want to do this, I would advise going with JB's method.