>I don't think that VFP transactions are that sophisticated.
>
>>
>>Yes, I know that the errors can be trapped, etc.
>>
>>What I evidently don't understand is what really happens in a transaction? I thought that when you do a BEGIN TRANSACTION, all updates/inserts are cached by VFP and the records don't actually get written to the table (table header locked) until an END TRANSACTION occurs.
>>
>>So, why the FIle is in use by another user...no it isn't. Not until the END TRANSACTION takes place.
>>
>>Nothing ever happens to the batch process. It always writes and never returns an error. It's the other users and processes, mostly in display information mode, that get these errors. They are not even trying to update anything.
>>
>>I don't get it...
>>
As always, Sergey, you are right on. Locking an entire table during a transaction lacks the word sophistication completely! Thanks for your input.

Scott M.