Quote Originally Posted by dilettante View Post
Most likely this isn't a DAO, ADO, or DAO + ADO issue.
So what is it ?
Because I can't think of another source for the problem than a (read or write) cache in ADO or DAO.

Adding transactions when you have a mix of ADO and DAO open connections in the same process seems like a recipe for deeper disaster.
I took care to check that the transaction was around a finite unit of work, so.. even i'm not comfortable with it, it should be safe. Even if the application is multiuser, users are not accessing the same data at the same time, too.