Steve Ellenoff <> 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..
>
> Is this how people are handling this or am I missing something
> obvious?
I use the where clause as the true catch.
Where tableKey = keyVar and LastUpdateDT = existingMemoryLastUpdateDT
If you don't have the last user and changed date time your on your own.
Stephen Russell
DBA / .Net Developer
Memphis TN 38115
901.246-0159
"A good way to judge people is by observing how they treat those who
can do them absolutely no good." ---Unknown
http://spaces.msn.com/members/srussell/
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.11.11/944 - Release Date: 8/9/2007
2:44 PM
_______________________________________________
Post Messages to: [email protected]
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.
