>>>>>Oops. Something else is happening now. If I delete several records from the grid and then save, they disappear from the grid. When I exit the form and re-enter, all but the last of the records I deleted have reappeared. I'm using pessimistic table buffering on all my tables.
>>>>>
>>>>Hi,
>>>>
>>>>Have you issued =TABLEUPDATE(.T.,.T.,'MyTable') before exiting the form?
>>>
>>>On closer inspection I realized that I am in fact issuing TABLEUPDATE(.F.,.T.), which explains it.
>>>
>>>I didn't reply for a while because we've had internet problems at our office.
>>>
>>>Before I go ahead and change my buttonbar class so it issues TABLEUPDATE(.T.,.T.) could anyone tell me what are the risks involved? At the moment, I'm using tables. I'll likely switch to views soon.
>>
>>There is not more risky to use views than Tables but it is a lot simple to use views to protype for remote access to a database. But, it requires a lot more job for using them.
>
>I was actually asking about the risks involved in TABLEUPDATing multiple records at once, in particular, when I deleted multiple records in a grid.

It's not more risky than do it without buffering, Now, you have to commit all your actions with tableupdate or revert it with tablerevert. But, you have to choose if you want to update multiple records (like in 1 to many) or update a record at a time.