On 8/10/07, Steve Ellenoff <[EMAIL PROTECTED]> wrote: > Sorry if the answer is obvious, but how are conflicts handled when > not using TABLEUPDATE() in VFP, ie, if you are rolling your own > UPDATE SQL commands and firing them back to the server? I assume the > problem is minimized if the code that generates your UPDATE is only > sending changed fields, but what happens if two users do change the > same field? It would seem that the *only* choice is that the last > user wins basically..
"Update using PK and Changed Fields" just like the option for views: UPDATE Customer SET LastName = "Jones" WHERE Customer.id = 37 and LastName="Smith" Fails if someone else has already updated the record so that the ID=37 and LastName="Smith" is not a match. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
