monkeytunes
Serf of the Jungle
- Local time
- Today, 06:34
- Joined
- Jun 8, 2004
- Messages
- 120
After poking around the forums and looking in Access help under "specifications", I see our pals in Redmond say that Access can handle 255 concurrent users. (I spit out my soda with a chuckle.)
After poking around some more, I see that the consensus is that Access will begin to choke depending on what those users are doing, alongside how much data is being pushed and pulled around.
Here's a bit of back and forth for you all...
1. My supervisors told me they want a database that can be viewed by up to 80 users (the odds of 80 people using it concurrently are slim to none, but not impossible...). Then they told me it should be accessible across the country, by users in branch offices. I said: "We need an Oracle/DB2/IIS/SQL backend. Access might work as a front end for this, but we need a big enterprise RDMBS."
2. My supervisors told me that, okay, instead of 80 full blown users, let's make it, like, 10 to 12 users that would actually be inputting data, and the others just need to view it. I said "That's a bit more feasible, but a national reach is probably more than Access, a fileserver at heart, can handle. Maybe Access with a frontend built from ASP...but probably still a big RDMBS would work best."
How accurate were my rebuttals?
After poking around some more, I see that the consensus is that Access will begin to choke depending on what those users are doing, alongside how much data is being pushed and pulled around.
Here's a bit of back and forth for you all...
1. My supervisors told me they want a database that can be viewed by up to 80 users (the odds of 80 people using it concurrently are slim to none, but not impossible...). Then they told me it should be accessible across the country, by users in branch offices. I said: "We need an Oracle/DB2/IIS/SQL backend. Access might work as a front end for this, but we need a big enterprise RDMBS."
2. My supervisors told me that, okay, instead of 80 full blown users, let's make it, like, 10 to 12 users that would actually be inputting data, and the others just need to view it. I said "That's a bit more feasible, but a national reach is probably more than Access, a fileserver at heart, can handle. Maybe Access with a frontend built from ASP...but probably still a big RDMBS would work best."
How accurate were my rebuttals?