Hallo Dieter Thanks to your reply.
We have recently seen several case, where "commit"s were lost. In our case, this was due to bugs in some of our products that registered the DA's too late with the transaction.
Currently I'm trying to create a product, which (should) work(s) with several databases. So I've tested it now against ODBC (ZODBCDA/M$-Access) and PostgreSQL (ZPsycopgDA). The problem occures only with ODBC.
Maybe, one of the products you use has a similar problem?
Aparently yes. The product I'm using is : ZODBCDA-3.1.0b2-win32-py21.tgz (83116 bytes) Date: 2001/11/15 Version: 3.1.0b2 for Python 2.1 (Development) Because it's distributed as a BINARY release, I've no chance (I don't even have the knowledge, i supose) to fix it. I'm using ODBC just for the case, a customer insists to have M$-Access. So I hope, nobody does ;-) Regards Dieter