Not without scripting. You can Use OnRecordCommit to perform a script and detect the error. Then check each field in turn and stop on the first one that's empty.
Thanks again for your help. At this moment I use a "general script" (OnRecordCommit) and check for 509 and 504 errors, and built in my own messages. Works fine. If I have to check the fields one by one, to find out which one is empty, I will have to make a script for each situation. That's no problem, just a little more work.
I was hoping there was a way to find the source field, because the original FM message (with ErrorCapture off) returns the field that is the source of the problem. (But also returns to the first field of the table).
PS. I am still working on my crash problem. TSGal asked me to send the file to them. As soon as I find out (or FM finds it out) what the source of the crash is, I will let you know.
One option is to set up the OnObjectValidate trigger on each field. This can be a general script using Get ( ActiveFieldContents ) to check the field's value.
Another might be to give each field an object name that matches the field name, then pass the list of fields that can't be empty to the script as a script parameter and use go to object to go to each field and test its value in turn.
Thanks for the additional suggestions Phil,
I tried them out, and the second suggestion works best. The first one works fine also, but a user can still "skip" a field (with the mouse). And if they skip a field, there is no "OnObjectValidate". So I will use the second suggestion.