UPDATE is ANSI SQL compliant statement while REPLACE is VFP native. If your app must be or should be ANSI SQL compliant so use UPDATE WHERE SET, INSERT INTO, SELECT FROM, DELETE FROM.
As for the slowing down, depends on how you do your coding. Basically, using SQL statements in manipulating data is slower than using VFP native syntax but the benefit would be scalability. Think it 100 times if you really need to do SQL compliant app. The are always trade-offs in doing this.
>Now that I think.... it was happening with local tables, nothing special, just updates or replaces like:
>
>"REPLACE ALL xxxx WITH 'xxxx' FOR yyyyyyyy = 'zzzzzz'
>
>or
>
>"UPDATE fffff SET xxxx = 'xxxx' WHERE yyyyyyyy = 'zzzzzz'"
>
>The first time I did, i was moderated slow, the second ( and third,4th....etc.) time I was soooo fast, but when I ussue a close data or a use, the system died!!!
>
>It wasn't matter which of the sentences used (UPDATE or REPLACE).
>
>Thanks
>Humberto
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."