Number of concurrent users

[iccsi]

I just learned that MS Access has limit of number of concurrent users
of 255.


I would like know how does it count 1?
Does it really count one user login the system for one or it counts
all the connections like queries?

For example, it a report is running opens 10 queries.
Does it count 10 concurrent users?


Your information is great appreciated,

 

[John W. Vinson]

I just learned that MS Access has limit of number of concurrent users
of 255.


I would like know how does it count 1?
Does it really count one user login the system for one or it counts
all the connections like queries?

For example, it a report is running opens 10 queries.
Does it count 10 concurrent users?


Your information is great appreciated,

Each user counts only once. There are limits on the number of open connections
but that's a different issue and shouldn't ordinarily cause problems.

HOWEVER... any multiuser application should certainly be "split" into a shared
backend containing the tables, and individual frontends containing the forms,
reports, queries, etc. See http://www.granite.ab.ca/access/splitapp.htm for a
thorough discussion.

 

[inungh]

Each user counts only once. There are limits on the number of open connections
but that's a different issue and shouldn't ordinarily cause problems.

HOWEVER... any multiuser application should certainly be "split" into a shared
backend containing the tables, and individual frontends containing the forms,
reports, queries, etc. Seehttp://www.granite.ab.ca/access/splitapp.htmfora
thorough discussion.

Thanks for the message,
Do you know the limits on the number of open connections?
Thanks again,

 

[Paul Shapiro]

Access doesn't limit the open connections, just the users. But if you're
hosting the data on a workstation OS, I think recent OS versions are all
limited to 10 connections. Since it looks like you're planning more than 10
users, you should be sure you can host the data file on a server OS. And to
emphasize what John already said, you DEFINITELY want to split your
application into a front-end db and back-end db. Only the backend (just the
tables and relationships) goes on the server. Each user should be running a
local copy of the frontend (forms, queries, reports, code) that is stored on
their local hard disk.

Each user counts only once. There are limits on the number of open
connections
but that's a different issue and shouldn't ordinarily cause problems.

HOWEVER... any multiuser application should certainly be "split" into a
shared
backend containing the tables, and individual frontends containing the
forms,
reports, queries, etc. Seehttp://www.granite.ab.ca/access/splitapp.htmfor
a
thorough discussion.

Thanks for the message,
Do you know the limits on the number of open connections?
Thanks again,

 

[inungh]

Access doesn't limit the open connections, just the users. But if you're
hosting the data on a workstation OS, I think recent OS versions are all
limited to 10 connections. Since it looks like you're planning more than 10
users, you should be sure you can host the data file on a server OS. And to
emphasize what John already said, you DEFINITELY want to split your
application into a front-end db and back-end db. Only the backend (just the
tables and relationships) goes on the server. Each user should be runninga
local copy of the frontend (forms, queries, reports, code) that is storedon
their local hard disk.






Thanks for the message,
Do you know the limits on the number of open connections?
Thanks again,- Hide quoted text -

- Show quoted text -

Thanks millions,

 

[inungh]

Access doesn't limit the open connections, just the users. But if you're
hosting the data on a workstation OS, I think recent OS versions are all
limited to 10 connections. Since it looks like you're planning more than 10
users, you should be sure you can host the data file on a server OS. And to
emphasize what John already said, you DEFINITELY want to split your
application into a front-end db and back-end db. Only the backend (just the
tables and relationships) goes on the server. Each user should be runninga
local copy of the frontend (forms, queries, reports, code) that is storedon
their local hard disk.






Thanks for the message,
Do you know the limits on the number of open connections?
Thanks again,- Hide quoted text -

- Show quoted text -

My applications link to 10 backend databases to generate the reports.
The reports have tons sub reports.
User get Too many connections Can not open more databases error
message when user print the report from preview, but it works direct
print without preview.

I just wonder that MS Access rerun the queries and report when user
print the report from preview to make too many connections and the
error message.

Yes, I should move our databases to SQL server, since the complex of
the databases and reports.
It seems our applicaitons and databases reach limitations of MS
Access.

Thanks millions for helping,