By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,027 Members | 1,271 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,027 IT Pros & Developers. It's quick & easy.

Concurrent Users

P: n/a
There seems to be a consensus that Access has a concurrent user limit
of 200 users. I am working on a system that currently stands at
approx. 1 gig and has a small number of users. However, there is a
project on the horizon that I have been asked to implement (within 2
months) where there will potentially be 1200 users accessing the
backend through a Cold Fusion Interface.

Whenever, I have been looking at this many users, I have always been
in a SQL environment, and load like this is a non-issue. I raised my
concern over the number of users that would hitting Access, and I am
more or less being told not to worry. The reason being is that there
is another, much smaller Access database in-house with a Cold Fusion
front-end. My source tells me that Cold Fusion opens only one
instance of Access (one thread) and Access sees all load through the
Cold Fusion interface as ONE user. Therefore load will not be an
issue and that I should not be concerned.

I have seen several instances on forums and elsewhere, where load
becomes an issue in Access. The info I hear on both ends of this
debate, doesn't match. If CF opens only one thread, I would still
think that Access would reach a load limit at some point. You can't
just keep adding users indefinately via one CF or .asp interface and
never expect performance issues.... Can You? At what point would
Access "Crap Out" in this instance?

Does anyone have any concrete examples or info about the scenario
described above?

I appreciate any info that people have! Thanks Tons!!
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
as many different opinions as there are in this ng no one in their
right mind would EVER suggest access as a back end for 1200 users.
that's insane. access is limited to 255 concurrent users. ask
whoever is propsing this absurdity to provide a proof of concept. it
will fail. a client server backend is the only way to go w/1200
users. u can always throw more hardware at the server if performance
begins to drag.

bc******@jeffco.k12.co.us (bluedolphin) wrote in message news:<37**************************@posting.google. com>...
There seems to be a consensus that Access has a concurrent user limit
of 200 users. I am working on a system that currently stands at
approx. 1 gig and has a small number of users. However, there is a
project on the horizon that I have been asked to implement (within 2
months) where there will potentially be 1200 users accessing the
backend through a Cold Fusion Interface.

Whenever, I have been looking at this many users, I have always been
in a SQL environment, and load like this is a non-issue. I raised my
concern over the number of users that would hitting Access, and I am
more or less being told not to worry. The reason being is that there
is another, much smaller Access database in-house with a Cold Fusion
front-end. My source tells me that Cold Fusion opens only one
instance of Access (one thread) and Access sees all load through the
Cold Fusion interface as ONE user. Therefore load will not be an
issue and that I should not be concerned.

I have seen several instances on forums and elsewhere, where load
becomes an issue in Access. The info I hear on both ends of this
debate, doesn't match. If CF opens only one thread, I would still
think that Access would reach a load limit at some point. You can't
just keep adding users indefinately via one CF or .asp interface and
never expect performance issues.... Can You? At what point would
Access "Crap Out" in this instance?

Does anyone have any concrete examples or info about the scenario
described above?

I appreciate any info that people have! Thanks Tons!!

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.