Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Transaction updates - causing others to crash?
Message
 
 
À
24/01/2010 13:27:39
Scott Malinowski
Arizona Fox Software LLC
Arizona, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Divers
Thread ID:
01445710
Message ID:
01445779
Vues:
47
I don't think that VFP transactions are that sophisticated.

>
>Yes, I know that the errors can be trapped, etc.
>
>What I evidently don't understand is what really happens in a transaction? I thought that when you do a BEGIN TRANSACTION, all updates/inserts are cached by VFP and the records don't actually get written to the table (table header locked) until an END TRANSACTION occurs.
>
>So, why the FIle is in use by another user...no it isn't. Not until the END TRANSACTION takes place.
>
>Nothing ever happens to the batch process. It always writes and never returns an error. It's the other users and processes, mostly in display information mode, that get these errors. They are not even trying to update anything.
>
>I don't get it...
>
--sb--
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform