Number of Users

[Guest]

I have been asked to investigate if we can use access to create a database
for use within my company. The database wil have around 15 / 20 users
writing to the database.

I have read post that mention that there limits of the number of people who
can read / write to an access database at the same time, is this true?

What are the pratical numbers?

If Acces is not suitable what would be the best alternative?

SQL 2007, with an access or VB front end possibly

 

[Keith Wilby]

I have been asked to investigate if we can use access to create a database
for use within my company. The database wil have around 15 / 20 users
writing to the database.

I have read post that mention that there limits of the number of people
who
can read / write to an access database at the same time, is this true?

What are the pratical numbers?

If Acces is not suitable what would be the best alternative?

SQL 2007, with an access or VB front end possibly

There is a limit to the number of *concurrent* users but AIUI you have to
factor in other elements such as network performance and user-intensity. To
optimise performance and protect against corruption you'd need to split your
app and give each user their own front end (GUI). In my experience 15 to 20
users shouldn't pose a problem to Access.

Keith.
www.keithwilby.com

 

[John W. Vinson]

I have been asked to investigate if we can use access to create a database
for use within my company. The database wil have around 15 / 20 users
writing to the database.

I have read post that mention that there limits of the number of people who
can read / write to an access database at the same time, is this true?

Yes: 255 concurrent users is the documented limit.

What are the pratical numbers?

That depends on many things - the design of your application, your users'
tolerance to delay and to concurrent update errors, the speed and reliability
of their computers and your network, etc. As a rough rule of thumb, 20 to 30
concurrent *updating* users (in a well designed app where the users will
rarely or never be updating the same record at the same time), and upwards of
100 read- only users should be managable.

John W. Vinson [MVP]