Muti-User Question - 400 USERS

  • Thread starter Thread starter Bret
  • Start date Start date
B

Bret

What is design and performance issues and concerns with an
Access front & backend application (split database) for
400 users. Not heavy usage throughout any given day.
Majority of users is strictly View Only.

thank you.
 
Bret said:
What is design and performance issues and concerns with an
Access front & backend application (split database) for
400 users. Not heavy usage throughout any given day.
Majority of users is strictly View Only.
Click to expand...

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
 
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..
 
Yes, you can have several million users, but as long as only a reasonable
number use the database at the same time, then you should have no problems.

So, if you have 10 million users, but if only 3 of them use the database at
the same time, you will be just fine.

Actually, the same goes for your car: You can have 1 million owners, but as
long as only a few people ride in the car, you should be ok.
 
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.
Click to expand...

The limit is on 255 users all simultaneously attempting to use the
database. If a user doesn't have the database open, they aren't a
"user" by this definition - and you can have any number of potential
users who might open the database someday!
SQL Server is the way to go but our hands are tied for
this project at present.
Click to expand...

Performance and frequency of corruption (if very many of these users
are going to be updating the tables) may make SQL look like a
bargain... and it's getting cheaper anyway. Do look into MSDE - a free
(included on your Access CD) version of SQL Server, at least as a tool
to speed development of your SQL implementation.
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
Click to expand...

CHeck out Tony's excellent webpage (http://www.granite.ab.ca/access)
and follow the recommendations on his performance FAQ. It's the most
comprehensive collection I've ever seen.
 
John Vinson said:
Performance and frequency of corruption (if very many of these users
are going to be updating the tables) may make SQL look like a
bargain... and it's getting cheaper anyway. Do look into MSDE - a free
(included on your Access CD) version of SQL Server, at least as a tool
to speed development of your SQL implementation.
Click to expand...

There was one reliable report of 100 users using an MSDE data storage.
Even though it starts putting in delays and throttling things back at
5 processes. Which is not the same as users.

But I don't know if MSDE would do a good job for 400 users even if
most of them were inquiry only.
CHeck out Tony's excellent webpage (http://www.granite.ab.ca/access)
and follow the recommendations on his performance FAQ. It's the most
comprehensive collection I've ever seen.
Click to expand...

Thanks for taking the words right out of my keyboard. <smile>

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
 
Bret said:
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.
Click to expand...

To be quite clear on this. 255 people can have the FE open to the
backend at any one moment in time. Of course thousands of people can
have the FE installed on their system.
SQL Server is the way to go but our hands are tied for
this project at present.
Click to expand...

I dunno about this one. Whoever sold the client/users/whatever on 400
users without doing some basic fact checking in the first place should
be nominated for the training position for the PHB (pointy haired
boss) in Dilbert's cartoon.

If that's you and I've offended your feelings well let me add that at
least you then came to your senses and asked about the pitfalls.

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
 
Back
Top