There is a way to set "Jet OLEDB:Transaction Commit Mode"?

G

Guest

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.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

ADO wants exclusive access to MSAccess 7
Configuring Jet connection parameters using .NET OLEDB coneection 3
Iteration of Large Result Set 7
Transaction scope aborting 5
Is there a way to automatically commit EWF? 1
connecting to a secure Access database 6
Is there a way to setup EWF to always commit? 4
I want Excel to determine the correct directory. 10

Top