How to determine the order in which fields are validated?

[dmontano]

I have a layout that has 4 fields that require a value to be entered via drop down lists and one field is a radio selection.

 

These 4 fields prompt the user to enter a value or else the record will not be created. They all work correctly - however, the order in which they prompt the user for a value is something I am not able to control.

 

The drop down fields validate as expected - by tab order, however, the radio selection is the first one to pop up requesting validation - even though it is further down the tab order - and further down the logical flow of the layout.

 

How can I set the order of how these fields prompt for validation?

 

Thanks in advance

[Norma_Snockurs]

How can I set the order of how these fields prompt for validation?

Fields are validated within any particular table in the order they were created. The tab order is not relevant.

 

Go 'Define Database' and view your tables' fields by 'Creation Order'. This will show you the order in which any validation will be made.

[dmontano]

Thanks Norma,

 

Looking in "Define Database" shows exactly as describe.

 

I am a little puzzled as to how I can alter this order. I would think that FM would allow some remedy for this scenario. Maybe there is?

 

I also think having to recreate the field just to establish the order is problematic as well - as all the other fields that require validation would have to be recreated in the appropriate order - and then if I were to change my mind....

 

I would think this should be a preference per layout that I could manage.

 

As it stands now, user is sent to a field, they select from the drop down - all is good; user selects "outside" of any field - they get a validation dialog related to a field further down on the layout. They have to make that selection before continuing - so they in essence would be jumping "out-of-order".

 

Any ideas?

Thanks

[Ender]

If you're validating by calculation, you can include conditions that it only would return a 0 (false) if the previous fields have already been filled in. Something like:

 

field2 validation (example: must be greater than 0):

 

isempty(field1) or field2>0

[dmontano]

Hi Ender,

 

My validation is quite simple for all of these fields. I simply need to make sure the user actually makes a selection - so I do not end up with half-filled in records.

 

My validation criteria for these fields are basically:

1. Is not empty

2. A member of a value list

 

I provide a message when validation fails - that tells the user which field needs to be completed.

 

Is this the only method you are aware of in how I can deal with this? If so, I will have to figure out how to apply what you have said. I am quite "novice".

 

Thanks,

David

[Ender]

I prefer to avoid field level validations altogether.

 

I use calculated flags and scripted validations instead. Calculated flags indicate when sections of a data-entry process are complete (or incomplete), and scripted validations check that required fields are complete before allowing navigation to the next section, or before marking the record as complete.

[dmontano]

Hi Ender,

 

Thanks for the response. I am floored at how much I do not know - I thought I was moving along quite well 2 months ago - then I hit a bump, the bump got larger and then more bumps popped up. Just venting.

 

So it sounds like the "tools" I have been practicing from the books I have been reading are not quite right in this scenario. Since it really bugs me how the validation prompt pops up out of sequence, I need to add to my toolbox on how to get around this annoyance. So how does one go about learning the technique you described, and should I burn it in my brain and use it instead of my previous "book" method?

 

I ask because it can take me a long time to figure some of these things out - and I have a growing list of items I still can not figure out.

 

Calculated flags and scripted validation? Off to read some more.

[Ender]

See here for a little more about my thought on validations:

 

http://filemakertoday.com/com/showpost.php?p=38338&postcount=90

 

As for learning the program, I guess that just takes time, research, and trial-and-error. Of course, forums like this can be a big help as well, for learning from other's experience or for debating ideas and methods. If you're a FileMaker developer, the annual FileMaker Developer Conference is a great training and networking opportunity.