| 3:53 am on Dec 3, 2004 (gmt 0)|
MS Access was never really built to handle a website. We have thrown a great number of concurrent users against an MS Access database without any problems. This might help you though:
| 1:09 pm on Dec 3, 2004 (gmt 0)|
I see from the table that the maximum concurrent users is listed as 255. That would be acceptable for a site built for a relatively small organization, such as I'm thinking about.
You said that you had thrown a lot of concurrent users at an Access db. You were talking about a web-based db, weren't you?
And the maximum concurent user limit brings up more questions:
a) What happens when the site gets overloaded? I don't know databases but I assume what we're talking about here is essentially a denial of service effect. Will the database just lock up or will the whole site crash?
b) If that site is a virtual host on a shared server, will that crash the other virtual hosts?
| 1:20 pm on Dec 3, 2004 (gmt 0)|
We had about 1,000 concurrent users at one time with no problems. I would not recommend this of course
The database wil typically stop responding. It might become corrupt. It might stop the server, depends on the server, etc.
Usually though, if your site is this busy, it does warrant SQL hosting
| 1:45 pm on Dec 3, 2004 (gmt 0)|
I think I'll give it a shot. As I say, for a fairly small trade association Access should handle it. And you can't beat the convenience, seamless and all that.
| 2:04 pm on Dec 3, 2004 (gmt 0)|
This is true. Plus it is very simple to upsize once it is done. Make sure tht you connection string is in one file just in case you are ready to upsize.