Access 2.0 odd transaction behavior 
Author Message
 Access 2.0 odd transaction behavior

I am in the process of a comlplex step-by-step conversion process from
Access tables to server tables.  At this time, I am implementing some
transactions which update native Access and SQL Server tables

Today, I had a deadlock problem on the server and decided to kill a process
which was part of one of these transactions.  Access responded by finishing
the transaction and committing the changes to the Access tables without
generating an error!  This, even though the server connection it had been
using for the SQL Server updates within that transaction had been killed.

Does anyone know why this would happen and how I can improve the integrity
of my mixed transactions?  Would Access 97 handle this situation more

Sun, 09 Jan 2000 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. Strange Behavior of Access 2.0 SQL

2. Wierd Access 2.0 behavior

3. Wierd Access 2.0 behavior

4. Transactions with Access 2.0 under WinNT 4.0

5. Odd behavior with Dates -A2K

6. Odd Behavior With CommitTrans

7. odd Add Note behavior

8. Externally adding tasks via SQL gives odd behavior

9. Odd recalc behavior with shapeobj.duplicate

10. Odd behavior when inserting TextBox1 into header

11. Odd behavior by

12. Very odd behavior with DataTable.Select


Powered by phpBB® Forum Software