Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How would you solve this one
Message
De
18/05/1999 10:07:51
 
 
À
18/05/1999 07:29:21
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00217516
Message ID:
00220004
Vues:
42
Thanks Dragan. I get it now ... I read the rest of the thread <g>

Bonnie

>>>>Begin transaction implicitly locks all records created and modified during the transaction. That's why the record containing the number is locked. I don't do an explicit lock, I don't see why I would.
>>>
>>>Whoa. I take back what I said in a previous post. Pascal, you are DEFINITELY using TRANSACTIONS wrong, if you're starting the transaction the moment the user starts editing the parent record. You only start the transaction during the Save routine, to try to lock all records at that moment. You don't use the transaction to hold all the records locked during the entire edit.
>>>
>>>- Rich.
>>
>>My turn to say "WHOA", Rich. < g > I thought that the way Pascal was doing it is the correct way to do transactions. How can you roll-back changes if you begin the transaction in the Save routine??
>
>You don't Save at all, so there's nothing to roll back. Rollback is provided primarily to revert the effects of partially successful saves, IMHO.
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform