Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
More RLOCK Stuff
Message
De
17/03/1999 14:18:06
Nancy Folsom
Pixel Dust Industries
Washington, États-Unis
 
 
À
17/03/1999 14:10:37
Ian Matthews
Up & Running Technologies Inc
Chestermere, Alberta, Canada
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00198638
Message ID:
00198769
Vues:
18
Then you're back to ISRLOCK and unlocking after the user releases the record.
Or a semaphore table of records in use.

A. You want to lock the record for a user if they are the first one to call up the record. Yes? then issue IF RLOCK() then go on...but you need to UNLOCK when they leave the record...which isn't necessarily the same thing as a tablupdate, right? I mean, usually there's a way for user to save a record w/o exiting it.

B. I'd probably prefer to use a semaphore table and not actually lock the record at all. I think this was suggested to you earlier so might not be what you want.

>Thanx Nancy but 'no go'. I didn't think it through. Obviously ISRLOCK will only work when a record is locked and the only time a record is locked using OPT ROW BUF is the split second when it is being written.
>
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform