Oh Oh Oh !!!

You know, this never made sense before.

So, turn on buffering when I start, then either post or revert after each record.

That makes a lot of sense! Thanks ...

One last question. When the form closes, which causes the table to close, I don't have to turn off the buffering either?


>Oh, no, not at all.
>
>Depending on the parameters for TableUpdate(), you can update changes to a single record, or have (and save) pending changes to several records.
>
>Personally, I prefer to have changes to only a single record at a time. This avoids potential problems, with the user forgetting to save for a long time, etc. Before going to another record, the user is forced to save, or undo, changes to the current record.
>
>In any case, there is absolutely no point in turning buffering on and off all time, as you do if I understood a previous message correctly.
>
>>Hilmar --
>>
>>No, I meant that the Save / Cancel buttons apply to each record they work on ... they can select a record, or add a new record, and then choose to not save their work. But this would apply just to the current record, not the entire batch they're working on.
>>
>>The way I read your comment, they either get to save all their changes or none of them, across all records.