Right, Thanks again!
>Another way to handle this problem is by adjusting SET REPROCESS setting or issuing RETRY in the error handler for this error.
>
>>I didn't know that. Thanks
>>
>>
>>>DELETE FOR locks a table header for duration of the command. If somebody else has the header locked already for INSERT INTO, DELETE FOR, UPDATE FOR, e.t.c., than the error will be generated. To avoid the header lock you can use
>>> SELECT TempItems
>>> SCAN FOR ProcBatch = .sProcBatchId
>>> DELETE
>>> ENDSCAN
>>>* OR
>>> DELETE FROM TempItems WHERE ProcBatch = .sProcBatchId
>>>
>>>
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people