Shared MDB Performance with Access and ASPNET Clients

[DavidT via AccessMonster.com]

Setup:
1) WebServer running an ASP.NET app linked via Jet OLEDB in web.config to a
shared MDB file on another computer.
2) DBServer is WinXP. All users of the database have modify permissions on
the folder where the backend MDB is located.
3) ClientMachine running WinXP. The ClientMachin app is an Access 2003 MDE
front end program file linked to the MDB on the DBServer.

Additional Info:
The ASPNET app is using OLEDB to connect while the ClientMachine app is a
combination of OLE (ADO connection) to get data from unlinked tables and ODBC
(DAO linked tables).

Problem:
1) If the ClientMachine app is running by itself, everything is fine. LDB
file created for ClientMachine, no performance problems. Can connect with
additional ClientMachine apps and still no problems.
2) If the ASPNET app is running by itself (no ClientMachine apps are
connected to the database), everything is find. LDB file is created for
WebServer/ASPNET account, no performance problems.
3) When both are connected (both ASPNET app and ClientMachine), the ASPNET
app slows down to a crawl. The LDB file is created on the DBServer and I can
open it and see both computer/security names. All is fine in the
ClientMachine app, but the ASPNET app is practically unusable.

I am at my wits end for trying to figure this out. I realize that switching
to a SQL database would solve everything, but I have a client that refuses to
migrate from Access MDB database and need to come up with some kind of
solution.

Thanks in advance for anything.

 

[Klatuu]

You say the users all have modify permissions where the mdb file is located,
does that mean read, write, create, delete? That is what is required.

 

[DavidT via AccessMonster.com]

You say the users all have modify permissions where the mdb file is located,
does that mean read, write, create, delete? That is what is required.

Setup:
1) WebServer running an ASP.NET app linked via Jet OLEDB in web.config to a

[quoted text clipped - 27 lines]

Thanks in advance for anything.

I was trying to imply that they have permissions over and above the required
ones. I currently have everyone set at Full and still the issue persists. Any
possibility it has something to do with connection pooling or a conflict
between accessing the database using both ODBC and OLE with ODBC winning out?

 

[Klatuu]

Is this database a front end or a back end?
It is a split database? If so, where does the front end reside?
Are multiple users accessing the same front end?
Can you describe how you are using OLE in this situation?

 

[DavidT via AccessMonster.com]

Is this database a front end or a back end?
Back end Access 2003 database with only tables.

It is a split database? If so, where does the front end reside?

Yes. Front end resides on each client computer.

Are multiple users accessing the same front end? No.

Can you describe how you are using OLE in this situation?

OLE used in the connection string of the ASP.NET web.config
(Provider=Microsoft.Jet.OLEDB.4.0).
Front-end Access client program file uses both OLE and ODBC. Front end is
linked to most tables in the back end database via DAO ODBC connection.
There are some tables that are not linked to the front end containing program
user names. Data from these tables is retrieved via ADO using the OLEDB
provider (Provider=Microsoft.Jet.OLEDB.4.0).
Yes. I have given all users full permissions to make sure nothing is left out.

 

[Klatuu]

Sounds like you have it pretty well covered. I don't see an issue here that
would contribute to the problem. I don't really have any experience using th
OLE connection you are using, but OLE does have a poor performance
reputation, but in your case it is probably necessary.

Sorry I can't be more help.

 

[DavidT via AccessMonster.com]

Klatuu,

I just appreciate someone responding. Thanks.