Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
BEGIN TRANSACTION does not protect my tables
Message
 
À
05/09/2002 17:31:32
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Maintenance bases de données
Divers
Thread ID:
00697283
Message ID:
00697322
Vues:
14
Hi,

just a guess: Is "Share Connection" still set to .T. for all your views? Does it help to set automatic transactions off with SQLSETPROP() and commit with SQLCOMMIT()?

Armin


>Hello, everyone
>
>I have a very annoying problem, which started immediately after installing SQLServerSP2, but I'm not sure is related.
>
>I use remote views in my app. All the views are sharing the same connection. Till yesterday, if I USE a remote view, get the connection handle with CURSORGETPROP function, SQLEXEC(handle,'BEGIN TRANSACTION'), that table was protected from other users. In another session of VFP or in an AccessXP project, I wasn't able to open the table and mess with it, until the transaction was commited or rolled back.
>
>Now I am able to trash completely the table (deleting all the records) and the transaction doesn't has nothing to say. It even returns 1 at 'COMMIT TRANSACTION'!
>
>Does anyone know what's happening?
>
>Maybe not related, but even so: I saw this behaviour before, but very seldom, only on some remote views I've modified in ViewDesigner. I deleted and recreated them and they worked ok afterwards. Now all of them have the same problem, no matter the app, no matter the database, no matter the SQL Server database.

Armin Neudert
Regional Director (Stuttgart) of German FoxPro User Group dFPUG

MCP for Visual FoxPro

Expert/Editor of the VFP section in the German Codezone community portal
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform