transaction and ms access

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Point Break - 14 Jun 2005 17:04 GMT

I have a vb application that is used by a variety of clients (xp and win2k)
that connect via ADO to a MS Access 2000 db on a network directory.
Once a client has successfuly completed a transaction, the other clients
suffer serious speed problems when recovering information from the same db.
It seems like the transaction commit continues to lock the data (from 10
seconds to more than a minute!) in the transaction.
Has anybody already encountered this problem? Can you help me please?

Reply to this Message

Kjeld - 28 Jun 2005 08:26 GMT

Yes!!
I use two separate connections, created by the same application (C#, .NET1.1
on Win2003 server).
Data is stored through connection #2 using a transaction.
After the transaction is committed and the connection is closed, data is
retrieved using a select statement through connection #1, that was open
before connection #2 was opened. The dirty data is returned instead of the
updated data.
If I re-open connection #1 before executing the select, the problem does not
occur. (but I don't want that, as opening the connection time after time
costs me a lot of performance).
(BTW: I use OleDb classes to access the mdb file.

Desperately looking for a better solution.

> I have a vb application that is used by a variety of clients (xp and win2k)
> that connect via ADO to a MS Access 2000 db on a network directory.
[quoted text clipped - 3 lines]
> seconds to more than a minute!) in the transaction.
> Has anybody already encountered this problem? Can you help me please?

Reply to this Message