>hmm so I looked at your code I always read buffering was to protect data during updating never quite got that part .Also i dont really follow your save code....nor do i trust mine
>I wrote code to a field then hit save then i browsed the data was there
>in the save button i had(tableupdate() then i added what you sent)
>
>then i ran the form again...wrote in a name then without pressing save i browsed the table...sure enought the new data was there(in the table) without i attempted to save. In that case the only way i could ensure that no data was saved without i wanted it done was putting a revert in the close button and upon destruction of the form now our saves dont work.:D is it because i have table revert when i close the form?

I believe the BROWSE will show the same data you see in the form - the values in the buffer. To see whether the changes have actually taken effect, open another copy of the form, and just look at the data through the form. Make sure to use a private datasession for your form. In this case, it will work almost as two different users.