>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?

All you said is clear, you just didn't say all...
I understand the save part.
Is cancel an option too? Telling the user that validation failed doesn't make much sense when he's trying to cancel.
So, again, how do you force valid to return .t. when the user is cancelling at the class level? I have the solution that involves DoDefault() calls in controls valid - maybe it is not that bad, in fact there might be only a few cases were I need it (when valid code needs to return .f. or 0). On the other hand, the code I put at the class level will execute for all controls that have no valid code on the forms - another little overhead... Maybe a clearer mind will say that this is the best you can do?