>To continue recent discussions about buffering....
>I always use optimistic buffering for forms, but find users sometimes inadvertantly are saving records when bombing out (quitting etc.)
>
>Is there a status flag to read to identify when a new record is in the buffer, but not saved yet? Then on exit a missed record could auto be reverted?
>
>No doubt for many this is a d-u-m-b question but I am close to going back to scatter/gather..
>
>tia

Jeff,

I have a transaction class that also handles the calls to the UpdateTable and RevertTable funtions. If a user exits a form without hitting the save button,
the .Destroy event of the form has THISFORM.otransaction.RevertDB() which runs the reverttable stuff flushing the buffers and not saving anything on the form.
This way, the user must hit the save button in order to save data.

Steve