>>>I don't think I'm asking for unlimited undo. Every app I've ever used has a save/cancel button and I expect cancel to undo any changes. To have it do anything else would be unheard of IMO.
>>
>>It certainly sounded like you wanted unlimited undo. I still think you need to explain more about what is happening. At this point I'm guessing that you're editing a record, your not saving it, you edit it again, cancel and the original value is lost? IF so, are your sure you are using table buffering and not record buffering?
>
>It's really only a single level of undo.
>
>Buffermode=5 for parent and child view.
>Parent form has save/cancel
>child form has save/cancel
>
>I select a child record (order detail line 1) in a grid on the parent form. Then I click edit. The child edit screen opens. I change a field called partnum from "11X" to "12X". I click "save" on child form. I have now returned to parent form. Then I realize I want to change order detail line 1 again. So I edit the same record. Now I change partnum to "13X". Then I decide not to change the record and I want partnum left as "12X" so I click "cancel" on the child form. So what value do you expect partnum to be and how does it get the value? I cannot tablerevert because that will change partnum back to "11X".

What does you Save button do on the Child form? Does it tableupdate the child or simply closes the child form? If the former, than your Cancel button would work just fine in your scenario.