>When you update TABLE.DBF, do you:
>1) RLOCK table.dbf, then
>2) INSERT INTO thread, then
>3) Update table.dbf
>
>***OR*** do you
>1) RLOCK table.dbf, then
>2) update table.dbf, then
>3) INSERT INTO thread

The call to the function to update the unique ID in TABLE.DBF is done prior to the INSERT INTO SQL. The function RLOCK(), update and UNLOCK. Then the program continues with INSERT INTO SQL.

>Your situation would definitely sound like a "dead;y embrace' to me EXCEPT for the fact of you SET REPROCESS *and* the possible length (time-wise) of update to phDBASE table.

There is no deadly embrace here.

As mentioned today, it all seems to be related to PHDBase.