Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Really dumb pessimistic buffering Q
Message
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Really dumb pessimistic buffering Q
Miscellaneous
Thread ID:
00112690
Message ID:
00112690
Views:
61
I have a form that I want to prevent multi-user editing on. I turned pessimistic buffering on and changed the global error handler to throw up a message whenever error 109 came up.

Works fine. If I open it twice, and make an edit to the record in one instance, I get the messagebox in the other instance.

HOWEVER....

If I save the changes in the first instance, and then save the (unmade) changes in the second instance, the second one overwrites the first one. What's the easiest way to deal with this? If I had the time and budget, I'd make it truly multi-user, with CURVAL() and OLDVAL() checking each field, but that isn't really an option.

My next choice is RLOCKing the record when I go into edit mode, but I'd rather work with buffering and implicit locking....
My blog
My consulting page
My home page

Member of the Trim Your Auto-Quote Campaign!
What's another word for thesaurus?
Next
Reply
Map
View

Click here to load this message in the networking platform