michaelrobertfrench
asked on
The database needs to be repaired or isn't a database file.
I have approx 15 individuals working in Access 2000 entering and editing records. 2 -3 times per day I get the error listed above.
Recently my network group switched to an AD from Novell. I never had this issue in Novell, but I can not definitely contribute the error to this change but I have my subspicions.
The data is entered through a very basic form directly into 1 table. Then individuals go into another form populated by a basic select query accessing the same table. The select query is used to review selected items for a group of processors. 2 - 5 processors may access this form/select query at a time picking and choosing their work. There is also one other form using a select query a second group of users access to obtain their work. Again, 2-5 people access this form at the same time as well. After 2 - 5 hours of use the error message above occures when a new user tries to access the db. If you are currently in the db you can continue to work and it does not effect you.
Any ideas? Please help.
Recently my network group switched to an AD from Novell. I never had this issue in Novell, but I can not definitely contribute the error to this change but I have my subspicions.
The data is entered through a very basic form directly into 1 table. Then individuals go into another form populated by a basic select query accessing the same table. The select query is used to review selected items for a group of processors. 2 - 5 processors may access this form/select query at a time picking and choosing their work. There is also one other form using a select query a second group of users access to obtain their work. Again, 2-5 people access this form at the same time as well. After 2 - 5 hours of use the error message above occures when a new user tries to access the db. If you are currently in the db you can continue to work and it does not effect you.
Any ideas? Please help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Agreed
All databases are heavy network users. To reduce the risk of corruption, these are things to do for any database:
1: Make sure your hardware is in top shape, all computers are routinely vacuumed to remove dust and lint and your network is set up correctly. Have all the machines on the same domain.
1: Have individual front ends on each machine. I created a database that checks the server for a newer copy of the front end, downloads it if needed, then runs it. You can get a copy of it at: http://www.nosuffering.com/Nelson/CheckForUpdatedFe.zip
2: Create a mapped drive for the backend or place the backend folder as close to the root folder and use only UNC path to the backend. Some people (and Microsoft) say the mapped drive is better, some say the UNC path is better. I have found it depends on the network setup.
3: Have the name of the backend and the name of the folders in the UNC path to it as short as possible meeting dos 8.3 naming specs and with only alpha numeric characters. \\server1\C:\db\db1_be.mdb
4: Don't run a local copy of the front end on the machine that has the backend -- best to have the backend on a server.
All of this is cutting down the number of times accesses need to be qualified, files need to be opened and closed and reduces the complexity of parsing the path all of which reduces the chance of corruption.