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

---

BTW instead of scan..replace...endscan might "replace for ... while ..." an option to prevent it + increase performance ? But it needs to lock table header as a downside (IOW exclusive).
>Cetin

Yeah, I was thinking of doing this.