Aceess speed

[Sunny]

Would it be any speed issues if I use access as front end and back end both
for about 25-30 users?

 

[Chris]

Well, if all 25 users are going to hit it at once, then
you could run into corruption errors. I would recommend
using SQL Server or Oracle for the backend.

Either way, have each copy of the front-end on the end
users computers. It makes it easier.


Chris

 

[John Vinson]

Would it be any speed issues if I use access as front end and back end both
for about 25-30 users?

Of course. There are *always* speed issues. <g>

If each user has their *own* separate frontend, with a shared backend;
if your network is fast and solid; and if your application is properly
indexed and well designed you should be ok. If you have more users
than 30 *concurrently updating* the database you may start to feel
some conflicts. If the users are predominantly in read-only mode you
should be able to get over a hundred without problems.

 

[Van T. Dinh]

Unfortunately, it depends on a lot of factors and since each situation is
different, I don't think anyone can give you a definite answer. Some of the
factors are:

* How well the database is design and implemented.
* How dynamic the data is.
* Which Access version you are using.
* The number of "Write" users c.f. the number of "Read-Only" users.
* Capacity of hardware/software on your network.
* How well your network hardware / software have been set up / configured.
* How busy your network traffic is.

There have been reports of Access databases that worked well with over 100
users (probably under optimal conditions). OTOH, we have seen problems
posted in these newsgroups in databases with one or only few users.

Personally, I look for an upsize path at around 25 but the primary reason is
*the importance of the database*, NOT because Access can't handle 25 users.
In my thinking, if there are 25 users using the database regularly, it is
important enough to have proper back-up and restore procedures for the data
(which Access only provides partially). I think of it this way: can I
afford 25 people getting paid but not doing productive work for a day or
two?

Another way of looking at it: if the database I develop doesn't work
properly / efficiently to the clients' expectation due to under-dimensioning
of the required software, the clients blame me as the developer, NOT the
software.

Which one should I choose?

 

[Michel Walsh]

Hi,


Also remember that a "workstation" is limited to 10 simultaneous network
connections. You need a "server" ( with the name Server in the OS ) to
increase that limitation.


Hoping it may help,
Vanderghast, Access MVP