Oops. You're right. I recently put SET EXCLUSIVE OFF in order to allow shared use. I should also say that this is vfp3, that I hope to get company approval for purchase of vfp6 soon, and that my TableUpdate() is wrapped in a transaction.

Actually, I just tested it again. Saving and reverting don't really take so long unless two sessions are on the same record. If they both edit the record, the errors are as expected. If one is displaying it and the other edits it, the speed of TABLEUPDATE()/TABLEREVERT() is slower. All of that makes sense. Thanks anyway.

>The header of the message and the body of the message seem to be in contradiction. Did you change SET EXCLUSIVE to ON or OFF?
>
>It's normal for TableUpdate() and TableRevert() to take longer with SET EXCLUSIVE OFF, because they have to check that the record/table is not in use before commiting the change.
>
>Be careful with SET EXCLUSIVE ON, not only no other user can use the table, but you cannot open another form within the same application that will use the same table (with private datasession).
>
>HTH
>
>>I have a legacy app originally used on one machine in which I only recently put SET EXCLUSIVE ON. TABLEUPDATE and TABLEREVERT are a whole lot slower now, taking as much as several seconds. The main table has only 6500 records, and there is a parameterized view selecting a few records from another table of 5700 records.
>>
>>I suppose that SHARED use of tables requires some overhead, but this seems excessive.