H
Herrdue
My department has about a dozen users who put their hours-worked into
an Access database I developed years ago. The problem is, once a month
we run reports and it seems that the datase gets corrupted quite
frequently when we are trying to run reports AND when users are
entering their hours. This has happened enough for me to believe it's
a case of too many users doing too many things in Access
simultaneously.
Can anyone suggest a means of lessening this burden on Access? For
example, if we moved all the queries and reports into a different
Access database, and linked them to the tables in the original, we'd
then have all the main tables in once Access db where the main users
would enter their hours, and then the people who do all the crazy
queries and reporting would be using a different one. Would this make
a difference? Or is there some other way to go about this?
an Access database I developed years ago. The problem is, once a month
we run reports and it seems that the datase gets corrupted quite
frequently when we are trying to run reports AND when users are
entering their hours. This has happened enough for me to believe it's
a case of too many users doing too many things in Access
simultaneously.
Can anyone suggest a means of lessening this burden on Access? For
example, if we moved all the queries and reports into a different
Access database, and linked them to the tables in the original, we'd
then have all the main tables in once Access db where the main users
would enter their hours, and then the people who do all the crazy
queries and reporting would be using a different one. Would this make
a difference? Or is there some other way to go about this?