Networks

Ask something
Discussion Locked

MS Access 2000

0 helpful
3 replies

by bytj

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I had a Access 2000 db located on one NT server. In recent months, an error occurs time and again, and is very annoying. Though I can fix it every time, I'd like to know why and how to fix it once for all.
The db server has about 12 users accessing to the same database.
I have a form with a lot of buttons. When I click one button, it will prompt me a dialog box for entering a customer id. If the customer id is found, it will produce a report about the customer. However, this button does not always work. Sometimes just nothing happens when clicking. If I go to "Tools | Compact/Repaire database", then that button will work again. I just wonder how this can happen and how to fix it.

3 replies

by glen_mcleod

The problem is with the number of connections that you are getting to the DB.

Access was never meant to be a large workgroup database, and the recommended maximum concurrent connections is around 8-10.

The application (depending on how it's written) could also be opening more than 1 connection per user, resulting in even more physical connections.

This corruption will continue to happen with this amount of users, it's just the nature of Access.

You might want to consider moving to MSDE in the short term (it's free with Access 2000), which will support up to about 25 concurrent connections (note: connections, not users).

Long term, you should start looking to move to a large RDBMS. Moving your databases from MSDE to SQL Server is a no brainer, but other products are good too.

Glen

by bytj

I finally found the problem by myself. The db is not properly designed. It is stupid that the system will prevent from producing a report simply because the printer is not connected.

This discussion is closed to new replies.