how many users can share access database on intranet

[rahul2310]

In my organization access(2010) database is created ,we are planning to put it on intranet.Databa se is not in FE and BE format.
So how many users can share that database at same time if it is on intranet.

[9815402440]

32 users can share data simultaneously.

[topher23]

According to Microsoft's website: Access 2010 supports a maximum of 64 connections per process with a limit of 256 concurrent open read/write connections per database.

But your best practice will still be to split into FE/BE to reduce the chances of data corruption. A shared front-end with no data will be at risk of code/object corruption, but that can be handled with a good backup procedure. The back-end would then be safer from data corruption, which is not as recoverable.

In my early days as an Access developer, I did exactly what you are proposing and constantly had to deal with locked recordsets and corrupt data. Only when I started practicing FE/BE did I get to stop the constant user support and get real work done.

[CJ_London]

You would also be better for each user to have their own copy of the FE. It gives you a problem of version control, but at least you can update the FE in a time of your choosing and not late at night when everyone else has gone home.

Also, just to check - you do not have any routines in your db which requires the creation of temporary tables? If so they will each definitely need their own FE copy

[zmbd]

I have reset the "best answer" as the one selected by OP has inaccurate information for Access2010.
----------

Access 2010 specifications (click here)

- Total size for an Access 2010 database (.accdb), including all database objects and data 2 gigabytes, minus the space needed for system objects.

Note You can work around this size limitation by linking to tables in other Access databases. You can link to tables in multiple database files, each of which can be as large as 2GB.

Tip For more information on reducing the size of your database, see Help prevent and correct database file problems by using Compact and Repair.

- Total number of objects in a database 32,768
- Number of modules (including forms and reports that have the HasModule property set to True) 1,000
- Number of characters in an object name 64
- Number of characters in a password 14
- Number of characters in a user name or group name 20
- Number of concurrent users 255

----------

In agreement wih both topher23 and CAintheUK: you should split the database and each client MUST have their own copy of the frontend or you will have issues with locked recordsets and in some unusual cases, corrupted data.

[rahul2310]

I have reset the "best answer" as the one selected by OP has inaccurate information for Access2010.
----------

----------

In agreement wih both topher23 and CAintheUK: you should split the database and each client MUST have their own copy of the frontend or you will have issues with locked recordsets and in some unusual cases, corrupted data.

thanks zmbd happy to konw that 255 users can concurrently access database but there is one problem database is already live on intranet so cant make any changes to database now.
I would like to know when exactly lock recordset error occours.
Thank you in advance.

[weeklydeals]

Please try to add 255 concurrent users and see, if 30 concurrent users tries to access the database, the performance of the server degrades significantly.

[zmbd]

weeklydeals:
Please read the question, it had/has nothing to do with performance.

However, to address that issue, as it can be a concern:

You will find that perfomance has much do with the hardware and the database design. On several of my splits, I have over 60 concurrent on a LAN without issues and it is mainly due to how the frontend/backend are designed, the highspeed backbone, and using the most up to date OS/Hardware configurations - and yes, I had help from professionals to streamline things on the software side.

Frankly, often our MYSQL and SQLServers are often much slower despite being on the same backbone and hardware (sometimes even with fewer users; however, that's a rare event :) ). The programmers admit that it has to do with the overall design of the databases and the need to work with legacy record systems.


rahul2310:
Record locking issues can not be easily predicted without know your database. It happens when two or more users access the same record(s) for create/write/modification at the same time in the same table. If you want more detail, then please start a new thread (^-^).