 Mart wrote:
Bluefrog wrote:
If you need reliability and data integrity for a relatively small application (thousands of records) that has a limited number of simultaneous users (10~30 max), then Access is fine.
|
Where did you get the 10~30 max from, on ms's website its defo in the hundreds.
Mart.
|
Perhaps my tendency to exaggerate the situation... 50 max.
How many times have we read about Access/Jet crashing? And what is the usual cause? Too many simultaneous users trying to access the same information.
MS has a free stress testing tool that you can use on a web app to see just how far you can push it. If you'd like to, create an Access DB with several tables, relate them, do some cross joins and insert them to create test data, make a web page to pull out some data using at least two joins, then stress test it for different loads. You'll see my point.
Point: You don't want to push Access too hard if you are relying on that information and you can't afford for it to fail.
Inside of an Intranet, you have a very controlled environment, and this is ideal for Access because you KNOW what you will be dealing with. Take that to the Internet, and you've got a world of unknowns. Take a multi-threaded web spider/bot that isn't set to allow time inbetween requests and just goes nuts making 100 requests at a time. That can be enough to bring a more complex Access based web application down.
My 10~30 should be taken as a (close to) worst case scenario.
Topic Options
Post Options
Thanks(0)
