Hi,
I'm using OleDb Provider for Jet and ADO.NET to connect to an Access 2000
Database.
My application spans various transactions and issues various commits in
sequence to this database (physically on a network share). Right after a
transaction is committed I need to read the information on the database. The
fact is that the commit "still not committed" in my next read.
I recently discovered that Jet works by default in asynchronous mode. To
guarantee the commit, I need to set the provider specific option â??Jet
OLEDB:Transaction Commit Modeâ?? to 1.
The problem is that I canâ??t find a way to do that in ADO.NET. The KB article
318161 says thatâ??s not possible.
Could someone confirm that itâ??s really not possible?
Thanks.