Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Rlock
Message
De
21/09/1997 14:16:00
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
17/09/1997 13:07:58
Shane Gilbert
Oklahoma State Department of Education
Norman, Oklahoma, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
Re: Rlock
Divers
Thread ID:
00050424
Message ID:
00050972
Vues:
29
>IF rlock() >REPLACE *fields*WITH *variables* >ELSE >wait window "Lock failed try again" >UNLOCK >LOOP >ENDIF >SELECT B >REPLACE "fields* WITH *variables* >UNLOCK > >It seems to me that there should be an UNLOCK right before SELECT B, and >then another rlock() before REPLACE fields in B. Also, does the LOOP >command retry the rlock or where does it go? The Unlock command will release all the locks, so once is enough. This kind of manual locking is rarely used, and the reasons may vary. One of them is that in some networks there were problems with implicit locking (had one case in 1991, been solved by next release of the network - but that is all the cases I've had), so some manual locking had to be used. Now this kind of problem is obsolete, never heard of a thing like that on contemporary networks - automatic locking will surely do good enough. Simply comment out the code starting with If Rlock() up to the EndIf. The Loop command should iterate the loop once more, skipping the rest of the commands till the end of the loop. It's supposed that the part of code shown here is inside some kind of Do While...EndDo, Scan...Endscan or For...EndFor loop.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform