field validation

[neldom]

I can't get around that every time I want to use a field validation It is triggered at the beginning and not at the end of a new record.

I want the validation to be triggered when I want to create another record or simply before I quit, so that the field is filled with the information intended for that field.

This validation issue is quite an issue for me. I'll appreciate any help on this.Thank you

[Digital Life]

You could do a script trigger that runs when you leave a record and the script would check the values in the fields you want to validate.

[Vaughan]

I can't get around that every time I want to use a field validation It is triggered at the beginning and not at the end of a new record.

No it's not. Validation only occurs after the record is committed.

Something else is happening after the new record is created to cause it to commit.

BTW please update your profile, it indicates you're still using FMP 8.5.

[neldom]

You could do a script trigger that runs when you leave a record and the script would check the values in the fields you want to validate.

Thank you, I will try that but something is missing in the concept of a having a field validated. Thx a million anyway!

[neldom]

No it's not. Validation only occurs after the record is committed.

Something else is happening after the new record is created to cause it to commit.

BTW please update your profile, it indicates you're still using FMP 8.5.

I am still FMP 8.5

[neldom]

No it's not. Validation only occurs after the record is committed.

Something else is happening after the new record is created to cause it to commit.

BTW please update your profile, it indicates you're still using FMP 8.5.

Simply put. You want each record to recognized that a field is not allowed to remain empty. You check that field under "not empy" in the validation option. Then,

you hit "New Record". It doesn't even allow you to go to the layout where the field is, that you immediately get this messages that the field needs to have information....but....?#@%@$?

There seems to be an out of time reaction to the validation and mostly a choose not to put this restrictions......but many times they are needed...

So the only way is to create a script? and if so: Why the validation options?

[comment]

Your description is not quite clear to me. If you try to go to another layout (or even another record) in the same window, Filemaker will commit the current record - or at least it will try. If you want to leave the current record uncommitted, open a new window.

[Vaughan]

Then, you hit "New Record". It doesn't even allow you to go to the layout where the field is, that you immediately get this messages that the field needs to have information

I'll say it again: this is NOT NORMAL BEHAVIOUR. The solution must have custom menus or script triggers that is modifying the default behaviour.

Post your file (zipped with confidential data removed).