REPLACE is still perfectly acceptable.

>I think REPLACE is also "single user", in that it locks the table header. Maybe things are "blowing up" in the REPLACE logic before a TableUpdate is even applied? You might want to check out using SQL-Update wherever you are doing a REPLACE.
>
>>I am trying to fix a multi-user system. I notice that updates are being done via the REPLACE command and then a TABLEUPDATE command is used.
>>
>>I want to be sure I understand what is happenning. Is this redundant. The forms use private data sessions if that is relavent.