Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Really dumb pessimistic buffering Q
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Really dumb pessimistic buffering Q
Divers
Thread ID:
00112690
Message ID:
00112690
Vues:
60
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?
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform