Access Database Failure

[mrstwin2]

We are currently using a MS Access database with 15 linked tables and from
the base table (150 columns) there are over 270,000 rows, here is my
questions:
1. Are we pushing Access too far at this time to support 160+ users with an
average of 16 users on at any one time?
2. If above is not over the limit, at what point can we start to look at
failure of the database.

Additional information:
We have stress tested with over 25% of the users on at once on the server
and it kept plugging away, the down side is the data went from a decent
download to a trickle where it would normally take 15-20 seconds to get the
data to 1-2 minutes per data request.

Please feel free to ask for additional information

 

[Douglas J. Steele]

While a lot depends on how well designed the database is, and what
percentage of your active users are updating, versus strictly reading the
database, you are definitely on the high side.

I hope you've got your application split into a front-end (containing the
queries, forms, reports, macros and modules) and a back-end (containing the
tables). Only the back-end should be on the server: each user should have
his/her own copy of the front-end on his/her hard drive.

 

[mrstwin2]

No the front end is also kept on the server. The person in charge thinks
they know all about how to best use it. The database itself has its good
points and bad points, there was very little thought into the tables and none
to the programming as almost everything is hardcoded in. I can thankfully
say that I didn't write this, just inherited it. All users are updating when
when they are in the system. It is a very active database.

 

[Douglas J. Steele]

If your users are sharing the same front-end, you've got a disaster waiting
to happen on your hands.

 

[mrstwin2]

Thanks Doug...that helps me out alot.

If your users are sharing the same front-end, you've got a disaster waiting
to happen on your hands.