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
simultaneously.

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
reliably?