Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Update conflicts
Message
De
24/07/2001 16:30:17
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
 
 
À
24/07/2001 15:30:56
Chuck Tripi
University of Wisconsin - Milwaukee
Milwaukee, Wisconsin, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00533337
Message ID:
00534647
Vues:
11
>Maybe I should explain little more clear on how I did it (and would apply it towards VFP 6.0 likewise). What I do is DISABLE all the fields on the form, and have a "Edit" button. In "Edit" (ClickEvent), it would have RLOCK() somewhere (I use R to make it easier to read). If successful, then the record is allowed for editing, if not, then a Messagebox() would display (or WAIT WINDOW as I did in FPW 2.6) that it "can not edit at this moment". So, that way, the others can look at the same record.
>
>There is only one problem (or at least I forgot how I did it in FPW 2.6) on how to REFRESH() the data on the other forms (if opened) that the record was just edited and the other user(s) that are looking at it while it was being edited. At this point (little Off Topic), what or how do you (anyone) do this, via refreshing the forms that others are looking at it? Maybe a Messagebox telling them it was "just updated, please refresh this form"? Anyone aware of Novell's "whohas.exe", could that be done with it????
>
>I am not aware if most VFP or any app developer do not have "Edit" feature? I think it is safe way that there can be no mistake if bump a key, overwriting something. I have a buttonbar that I use on almost all the forms (Save and Revert only ENABLE upon clicking the Add or Edit):

Sure, you can have an "edit" button. But you can also allow users to edit directly, without first pressing "Edit". I don't see any problem there. If the user changes data accidentaly, he can press "Undo" to undo changes (TableRevert()). If the user tries to change to another record (assuming you want to save one record at a time), the user will be asked: "Do you want to save changes?".

The additional step for the user, to press "Edit", is unnecessary burden for the end-user.

Please see how this is implemented in major frameworks. Some will let you download trial versions and/or sample applications, for instance, Visual Extend (www.devigus.com).

I strongly suggest to use Optimistic Buffering, rather than rlock(), most of the time.

Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform