My rule of thumb for transactions in VFP is: if I'm updating multiple tables, usally one record each table I wrap in a transaction to ensure all tables are updated before I give the record saved dialog to user. However I dont use transactios for batch processing, due to implicit locking and novell limitations. You can always ask for NT. You have to creativly code big batches in VFP on Novell.
Jeff Hart

>I'm using Optimistic Table Buffering. After all the records are modified, the actual TABLEUPDATE() is wrapped in a TRANSACTION. Is this a problem?
>
>
>>If It's wrapped in a transaction you are implicitly locking each record. And If you're using novell it defaults to max 2000 locks, Net admin can change this but may not want too.
>>take it out of the transaction and release the locks
>>Jeff Hart
>>
>>>>>I have some code that SCANs a large number of records in a table and does some stuff with each record, including a REPLACE. On particularly large tables where a lot of records are processed, the server is giving a message that the record lock threshhold has been exceeded and the computer freezes up. Shouldn't the REPLACE command lock and unlock the records automatically? Why would a series of REPLACES cause a problem?
>>>>>
>>>>>Thanks.
>>>>
>>>>

---

Is it Novell ?
>>>>Cetin
>>>
>>>Yes, why?