My app works against an Access 2000 database, and it works fine except I get very slow response time if anyone has the database open. The database itself is just used for data, no forms or anything like that. But if I have the db open in Access, even if I don't have any tables or anything open, just sitting looking at the list of tables, my VB.Net app will get very slow response from the database. Something like 5-10% or normal speed. If I close the database window, my app will suddenly snap to life. I am using mostly oledbdataadapters to read and populate a dataset. Is this some kind of locking issue or something?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Access DB is super slow when someone has db open
- Thread starter jmille34
- Start date
Why are they using MS-Access to look at the database? Shouldn't they be using your application to manage the data?
Chip H.
____________________________________________________________________
Donate to Katrina relief:
If you want to get the best response to a question, please read FAQ222-2244 first
Chip H.
____________________________________________________________________
Donate to Katrina relief:
If you want to get the best response to a question, please read FAQ222-2244 first
- Thread starter
- #3
Because it is still in development, but it also occurs if two people have the app open against the same database. I was just using the example of having access open at the main menu to give a general idea that it does not only occur during active reading/writing to the database.. if anyone has the mdb file "open" to any degree, it seems to occur.
- Thread starter
- #4
ThatRickGuy
Programmer
Access was never really designed to handle multiple users well. I would recommend moving the database to MS desktop SQL Server db (MSDB? someone here knows the acronym). Or to another multi-user environment (SQL Server, Oracle, MySQL, etc).
-Rick
VB.Net Forum forum796 forum855 ASP.NET Forum
![[monkey]](/data/assets/smilies/monkey.gif "[monkey] [monkey]")
I believe in killer coding ninja monkeys.
-Rick
VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.- Thread starter
- #6
Yeah, I know.. I've been pushing for an active server for months for security reasons, but it's not really an option with our situation. And we have had really good success using the access database setup. The performance is really quite good, and it generally works well. We did a test with 60 simultaneous users with our old product, and it didn't slow down at all. I think Access gets a bit of a bad rap sometimes. The only thing is my new vb.net app has a problem with it if anyone has the db open even a little.
Oh, and I think it's msde..
Oh, and I think it's msde..
ThatRickGuy
Programmer
Not sure how someone has a database open only a little. And yes, Access has a bad rap, and for a reason.
If you have previously had 60 simultaneous users with out a performance hit, I would suggest looking at which connection drivers were used. It could be your old app was written in VB6 with DAO (MS:Access Jet Direct drivers) which would have been optimized to hit Access. I'm not sure how the ADO.Net drivers stack up against DAO for Access. If that is the case, you may want to use the DAO drivers to connect. You may need to create a wrapper class that will use old COM references to use DAO to connect (not sure if DAO is in .Net) and expose the data as ADO.Net though.
-Rick
VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.
If you have previously had 60 simultaneous users with out a performance hit, I would suggest looking at which connection drivers were used. It could be your old app was written in VB6 with DAO (MS:Access Jet Direct drivers) which would have been optimized to hit Access. I'm not sure how the ADO.Net drivers stack up against DAO for Access. If that is the case, you may want to use the DAO drivers to connect. You may need to create a wrapper class that will use old COM references to use DAO to connect (not sure if DAO is in .Net) and expose the data as ADO.Net though.
-Rick
VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.- Status
Similar threads
- Locked
- Question