>Carlos, you can store the record number of the active row in a form property, and compare the stored value with the new one in AfterRowColChange. If the row is changed, go to the old one, do your calculations then return to the new one and store the value. There's probably a simpler way - I'll think about it.
>
>Barbara

Barbara, the problem is biggest: each time the user adds an item and validates it with the command button, i ask him to save changes, if yes =tableupdate(), if not =tablerevert(). With rowbuffering that's not possible. In the aftercolchange event, record has yet updated and i can't revert.
If the user changes values of a record, i need to know the oldest values via oldval(). With rowbuffering, in the aftercolchange that's not possible.