>>I have 5 tables in a data environment in a form. I don't really want to use table buffering, but then how can I keep from writing changes until I do a tableupdate? In row buffering, changes are committed when the record pointer moves.
>
>it send the updates when the record pointer moves on the specific table nothing will happen if you move the record pointer of another table
>
>or if I didn't understad you correctly what is the situation you have trouble with?
>
>Arnon

More info...sorry, I guess I didn't complete the picture. I'm using a pageframe with 10 pages to input/edit data on injury accidents for the state of Colorado. Each page contains data from a different table in the environment, such as doctor info, insurance info, etc. It seems that when I go from page to page, I lose the advantage of the buffered data. I have a "Save" and "Cancel" buttons on the 1st page, and would like to base the final decision on whether or not to save all data changes/entries on the click of the "Save" or discard the session with a click of the "Cancel". But when I go from page to page, the changes for that table are saved without going through the button. Clear as mud???