Require not empty issue

[AvrioTech]

I have a layout where someone fills out 6 things

CompanyName, Address, City, State, Zip and Phone

I filemaker to require these fields to be filled in, so I went to define fields => Validate during data entry + Require Not empty + Desplay custom message.

This doesnt work the way I would like. It pops up 6 pop up dialogs if nothings filled it.

1) Is there a way to make it one dialog box instead of 6 that says you must fill in xxxxx + xxxxx (based on a calculation).

2) Is there a way to validate it before it goes to the next field?

Thanks

[Genx]

You might want to take a look at a free plugin called EventScript -- though i use a calc and a simple image to tell a user if a record is "valid"...

E.g.

Let(

valid = not IsEmpty(field 1) and not IsEmpty( field 2) and not IsEmpty(field 3) //etc. etc. ;

If(valid ; "imagewin:/C:/Documents And Settings/My Pictures/Valid.jpg" ; "imagewin:/C:/Documents And Settings/My Pictures/InValid.jpg"

)

[CoZiMan]

Phew, multiple questions and problems.

To the first question:

1. Yes if you only test once - your next question cancels this.

2. Yes if the calcs are interdependent.

So, to test once you can do so at a 'submit' script and test all fields, highlight the incorrect fields, and return the user to the data entry.

To test multiple times within the entry process you would create cascading calcs based on the success of the previous field entries.

You could also graphically change the display to give the user feedback at each step of the process.

This is a lot more work, but probably more satisfying for the end user.

Another option is to use a script based DisplayDialogue entry process to loop until the entries are valid.

This seems the simplest as you can control all the process and the display, while keeping the options available for all the different fields available i.e. What if the user DOESN'T want to enter a name, only the company? A script can override the internal validation if you wish and then set other flags to allow for further processing.

You'll also be able to use the SetVariable() statement to create a local variable which doesn't get entered into the record until AFTER the validation, still leaving the validation intact but not giving you all those annoying messages.

K?

[CoZiMan]

Hi Genx, we seem to be submitting replies at throughly the same rate !

I'm bowing out now, good hunting! :)