>>I meant that you could have a button accepting new or edited record. Most likely, it comes down to the binding again. 'Details' container fields should be 'bound' to custom 'detail' object properties, not to view/CA/cursor fields. This way user never enters to the grid, your code does it and it may include all needed validations.
>
>I think we're talking about different scenarios. You're proposing to have one record editting at the time. Usually I use similar approach but in this particular case I allow multiple records editting at the same form.
>
>I'm thinking that the only reliable way would be to loop through all records which were touched (using GetNextModified function) and check each record.
>
>A bit tedious, but I do not see a way to do it using direct control validations.

It's not one 'record' at a time. It is one record set of values at a time. Later, before Tableupdate, you may use GetNextModified (i use it sometimes, it is not tedious at all), but it would be relevant only if something was modified directly in grid.