Tony Toews: Muti-User Question - 400 USERS

[Bret]

thank you, this helps.
Just want to be sure, does this mean that more than 255
users MAY HAVE ACCESS to this program but only up to 255
can use at same time? Sorry for ignorance, just need to
be clear on this.
SQL Server is the way to go but our hands are tied for
this project at present.
Also, if front end performance is slow when linked to the
network backend mdb, can anything be done by IT group to
boost the server performance? I have optimized the
frontend as much as I could based on the suggestions found
in the "MS Access 2000 Development" book

thanks again..

-----Original Message----


400 users isn't possible. Jet, the database engine under the hood of
Access only supports 255 users.

If you only had 10 or 20 users doing updates and then hundreds of
users inquiring and reporting likely wouldn't be a problem except for
the 255 limit of course.

I'd consider SQL Server as a backend in your situation.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
.

..

 

[Douglas J. Steele]

Any number may potentially have access. And while the official specs say
that you can have 255 concurrent users, it's extremely unlikely that you'd
ever be able to support that many in actual use.

 

[Albert D. Kallal]

Also, if front end performance is slow when linked to the
network backend mdb, can anything be done by IT group to
boost the server performance? I have optimized the
frontend as much as I could based on the suggestions found
in the "MS Access 2000 Development" book

You don't say after how many users the application starts to slow down. Is
it slow with 40 users, but ok with 20 users? You need to give some
ideas/numbers as to "when" the database starts to slow down.

After how any users in the database at the SAME TIME does the application
start to get too slow?