Hilmar --

It appears like I'm closer ...

If I try two sessions, both can update records. However, if they both try to edit the same record, the second user who tries to do so just hangs until the first user releases the record.

I'm only using CURSORSETPROP once on my table, with a value of five.

Any further suggestions?

>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.