Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Very weird update conflict problem
Message
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
01137428
Message ID:
01138863
Views:
13
Hi Arto,

I cannot even tell if the second one will work w/o running a test. For that reason I would never use it.
I work a lot with MS SQL Server so it's naturall for me to use something that works in both in VFP and MS SQL Server, like UPDATE. The UPDATE may be slow compare to REPLACE...FOR because UPDATE locks record by record and REPLACE...FOR locks a table header.

>Is next preferrable
>UPDATE v_zips ;
>    SET dealerid = zips.dealerid ;
>  FROM v_zips ;
>  JOIN zips ON zips.zipcode == v_zips.zipcode
>
>than
>
>* set order to 0 && ??
>replace v_zips.dealerid WITH zips.dealerid ;
>   FOR v_zips.zipcode == zips.zipcode IN v_zips
>I have never use UPDATE, I just and just even rember such of command! But is there an advantage to use it - I dont know.
>
>
--sb--
Previous
Reply
Map
View

Click here to load this message in the networking platform