How many users can Access handle on WAN

  • Thread starter Thread starter pat \(removethis\)
  • Start date Start date
P

pat \(removethis\)

We are in the process of creating one central Access
database for about 40 users. Is it feasible to keep using
Access if we implement Terminal services as our connection
to the server using Server 2000? I will split into
fe/be. The number of user's that will simultaneously be
modifying, or changing records may be 20 at any given
time. At what point do we switch to SQL server?
 
A TS application is really no different than a traditional LAN application:
each user should be given their own copy of the frontend (usually on a
folder on the server), each user logs in to the TS and opens their OWN copy
of the frontend on the server, and that frontend would connect to the
datatables.

A well designed access app can handle 20 concurrent users, depending on what
they're doing. Your decision to upgrade should be based more on data
integrity than performance; there's no guarantee that switching to a
client/server will give you better performance (often you get worse
performance, especially is you do nothing more than link the tables).
 
-----Original Message-----
A TS application is really no different than a traditional LAN application:
each user should be given their own copy of the frontend (usually on a
folder on the server), each user logs in to the TS and opens their OWN copy
of the frontend on the server, and that frontend would connect to the
datatables.

A well designed access app can handle 20 concurrent users, depending on what
they're doing. Your decision to upgrade should be based more on data
integrity than performance; there's no guarantee that switching to a
client/server will give you better performance (often you get worse
performance, especially is you do nothing more than link the tables).

"pat (removethis) @nebrace.com"
in message news:[email protected]...


.
Would you suggest any books on the subject to help us
along the way in this implementation?
 
Back
Top