Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Strange update conflict behavior - mySQL backend
Message
 
 
To
01/03/2007 02:04:27
Vladimir Zhuravlev
Institute of the Physics of Earth,Russia
Moscow Region, Russia
General information
Forum:
Visual FoxPro
Category:
Client/server
Environment versions
Visual FoxPro:
VFP 8 SP1
Miscellaneous
Thread ID:
01199534
Message ID:
01199958
Views:
15
>Hello Greg
>I have seen similar things with Oracle
>Use key field only or key+timestamp
>It will not be error in this case.
>If you need to compare also updatable fields, do it yourself
>I mean before saving data make query of the same record to new cursor and compare data you have (oldval()) with this new data from server
>If all was the same, make =tableupdate()
>If something was changed, inform user, if he wants to keeep data or change
>it on new one.

Hi Vladimir,

In the code above did you mean tablerevert() if data were not changed?
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform