>Automatic means you do only record level validation?
>On your "detailed payables screen for a specific vendor" on your web site: I push the Add button, then type in an invalid invoice number (say, one that already exists) do you return .f. or just wait for the save code to tell what's not right. What triggers the save when it is not periodical, leaving the last control?
>Yes, Yes to all, No, Cancel :)

Sorry, I should have been more clear.

I do record level buffering because if there's any problem saving a record that you were working on, say, 5 records back, it gets too confusing for the user. So, evey time the record pointer moves, I save.

I have a valid method for any object that requires validation, and that will kick in if the user leaves that object. The real issue here is if the user is still on an object and clicks the Save on the toolbar, or if they try to move the record pointer, what happens to the current object, and what happens to any record level validation? What I do is simply tell the user of any validation that failed, and cancel the action they were trying to do (save or moving the record pointer).

Does this help clear things up at all?