I have a rather lengthy transaction that entails numerous updates to 
several tables.  The problem I run into is that after I commit the 
transaction, I run a subroutine which does basic cleanup (closing 
recordsets, setting object variables to nothing and resetting boolean 
flags).  After that, I close the connection the transaction is based 
upon.  Very intermittently, I get an error that states I can't close the 
connection because a transaction is still open.  When I reload the same 
record and rerun the routine in the debugger ( trying to find the error), 
it runs fine -- no error.  My question is thus -- do ado transactions 
delay write or update if they are very large?  I think this may be the 
problem because it never happens when I step through using the debugger, 
thereby giving the transaction time to complete before the connection is 
closed.  I remember something about DAO having an option to immediately 
flush all the changes in a transaction to the database.  I'm researching 
to see if ADO has the same feature. Like I said, this is a very 
intermittent bug.  Any help is much appreciated.

Greg Busby