My employer had used Access 97 to store a database for a consumer relations department.
The database crashed often, would not let more then 10 users in at once without crashing again.
It held thousands and thousands of records, and bogged down horribly
The entire database corrupted when someone sneezed, and it was generally hated.
I have had a few ’97 databases corrupt on me before.
We have had Access 200 for a few years now.
I have not had a database corrupt on me yet… but management is fearful of using it.
I have not tried numerous users in my access 2000. I will need 25 people in it at a time.
I was given the go ahead to roll out my access database to replace the nasty excel spreadsheet they were using.
(I am also getting sick of uploading them to run reports in access)
I was adding the users 1 at a time. So far so good.
Until yesterday
Yesterday, 1 record in a table in my new database corrupted. (not the whole database)
I used a query to auto populate information based upon another entry.
It was pulling info from a linked table from another access database on a shared network drive.
I need to decide if access will be able to pull the weight of 25 people’s data entry.
This corrupted record concerned me, because it shut the function of the entire database down. (on my day off no less!)
Here are my questions :
On access 2000:
1.)What is the highest number of users at once that you have ever seen?
2.)Would a query cause corruption more then VB dlookup? (Which I haven’t used, but I can learn)
3.)What practices and designs are the most common causes for database corruption? (Best practices please)
4.) Is there a way I can work about 1 corrupt record without shutting down everyone?
(All of their data was feeding into 1 table)
Thanks for your input!
-M
The database crashed often, would not let more then 10 users in at once without crashing again.
It held thousands and thousands of records, and bogged down horribly
The entire database corrupted when someone sneezed, and it was generally hated.
I have had a few ’97 databases corrupt on me before.
We have had Access 200 for a few years now.
I have not had a database corrupt on me yet… but management is fearful of using it.
I have not tried numerous users in my access 2000. I will need 25 people in it at a time.
I was given the go ahead to roll out my access database to replace the nasty excel spreadsheet they were using.
(I am also getting sick of uploading them to run reports in access)
I was adding the users 1 at a time. So far so good.
Until yesterday
Yesterday, 1 record in a table in my new database corrupted. (not the whole database)
I used a query to auto populate information based upon another entry.
It was pulling info from a linked table from another access database on a shared network drive.
I need to decide if access will be able to pull the weight of 25 people’s data entry.
This corrupted record concerned me, because it shut the function of the entire database down. (on my day off no less!)
Here are my questions :
On access 2000:
1.)What is the highest number of users at once that you have ever seen?
2.)Would a query cause corruption more then VB dlookup? (Which I haven’t used, but I can learn)
3.)What practices and designs are the most common causes for database corruption? (Best practices please)
4.) Is there a way I can work about 1 corrupt record without shutting down everyone?
(All of their data was feeding into 1 table)
Thanks for your input!
-M
