I'd like to start this thread in order to get various different opinions on Access robustness with more than 10 users. Lets say reasonably current Client and Server hardware along with at least 100Mbps ethernet. Frontend on local Client and backend Jet 4 on Server. Commercial type applications meaning fairly extensive I/O. Lets see if we can get some responses from those with real world applications. Might be of benefit to quite a number of us. List your client and server hardware/software along with your experiences. Have you considered changing the backend to SQL or similar? Pros and Cons?
thanks for your valuable opinions.
Just my two cents but when dealing with Access the hardware/network config is not as important since it's a file-based db system. I have built data intensive intranet applications with access as the backend and had no problem with up to 40 concurrent users, but with an actual client backend ran into difficulties after about 15. If you are going to use ADO I would try to use disconnected recordsets as much as possible to minimize the work the db actually has to do. This is why the web can have more concurrent users than a traditional client server app. I believe ADO.Net is usually done in a disconnected setting so maybe you can get more users that way.