Maximum concurrent connections in ms access

Question

What are the maximum concurrent ms-access connections?

Answer 1

Not too much. What are the MS Access access restrictions? contains some information with links to Microsoft KB articles and other resources.

Answer 2

In theory 255, in practice it depends well. If they are mostly readable and the network you are on is fast, then I saw 100+ no problem in a well-written database. On the other hand, I am sure that the same horrible database stories will appear that will be damaged with two users. Yes, it can happen, but if you create a good database and are realistic about what you do with it, you can get an amazing amount of users hanging on one.

In the long run, you may need to see a free (express version) SQL server for a higher number of users.

Answer 3

Literally, "Jet kernel versions 1.1, 2.0 and 2.5 can only be used by 10 client applications on the same machine." Starting with Jet 3.0 there is no such limitation. See this link: http://support.microsoft.com/default.aspx?scid=kb;en-us;154869

Answer 4

In my experience, 10 concurrent users are starting to cause problems. I am sure there are examples with very small datasets that work well with many users.

Access may be good for some applications. There seems to be a lot of passion in this thread.

The key concept to understand here is that there is no server. EACH QUERY will pull the ENTIRE table over the network.

If its JOIN, EVERY QUERY will pull EVERY table connected over the network. This is because the JOIN engine is on your desktop.

It does not matter where the access file is located. At best, it is located on the user's main desktop machine. Everyone else should use the network to access data.

If you have a 100k table and you want id # 1042, you will pull out 100k * Record the length of the data over the entire network, and then filter out everything except # 1042. It cannot cache, because your colleague may have changed the following record. which you want to look at.

I do not think that this is necessarily the number of simultaneous users in the access database. I think that the number of people at the same time pulls a significant part of the data over the network every time I press a button.

Network load / network latency will increase as the number of counters increases, the number of records increases, and the number of users increases. Perhaps a multiplier effect. Confirm this if you have remote data centers (encryption), vpn users (encryption), users on different continents, etc. Etc. Etc.