Hi Evan,

Yes the FOR Expression that I'm using is Rushmore Optimised and only one field is being updated. I'm going to give UPDATE - SQL a try.

Thanks for the Help,
Gavin...

>Hi Gavin,
>
>I believe that VFP locks the table *header* on a REPLACE...FOR statement.
>
>However, is your FOR expression Rushmore optimizable? It seems to me that in the dark recesses of my (admittedly swiss-cheese) memory, I recall that if it is, and you're updating only one field in a single table, VFP does *not* lock the header.
>
>(searching internal FAQ's...that might take a while)(bg)
>
>HTH.
>
>>Hi All,
>>
>> An App that I'm working on has a requirement to Merge Company and Contact Records. I was thinking of doing something like:
>>
>>

SELECT contacts
>>
>>REPLACE companyid WITH nNewCompanyId ;
>>    FOR companyid = nOldCompanyId

>>
>>What I'm concerned with is that in FPW2.6 issuing a REPLACE with a FOR Clause would lock the Table ( Effectively that same as issuing an FLOCK() ), does anyone know if the same problem exists with VFP6.0? Any suggestions or different thoughts on ways to achieve the update would be appreciated.
>>
>>Thanks,
>>Gavin...