Hmm, do you think it could be the number of users connecting to the DB simulateously? I don't use access as a backend (it sounds like you are though), so I wonder if that's why I've never had this problem.
I found a post that might help on google groups. One good point he made, I thought, was that if you use bound form, then every time it's opened, a connection to the underlying recordset will be opened.
Yes, we have a number of databases which are used concurrently by 50-100 users, with few problems. In certain "high volume" databases you may run into "record locking" (which is really page locking of 16 KB, I believe.). However, you can adjust the Record Locking "levels" in Tools ---> Options ---> Advanced, clicking on the "Edited Record" button, so that there is minimal locking.
I believe that there is a limit to the number of people that can have an
Access file open at the same time (about 256, I believe). But there are ways around this.
First would be to use SQL Server as a back-end. Second would to use UNBOUND forms for everything in the front-end (using SQL Server or Access as a back-end) and have absolutely NO linking of the front-end to the back-end. Instead, all data is called up and/or written to the back-end via SQL commands. In short, the user is connected to the back-end file only for the miniscule fraction of a second that the record is pulled into the form or being updated back into the table. (However, unless you are talking a really high production environment, e.g., have 1000+ users continuously entering data into the same back-end all day long non-stop, this probably isn't necessary.
---Phil S.
This may not be applicable to you though.
I am kinda curious as to what's causing your problem. If you find a solution before somebody here does, I'd be interested to hear what you did to fix it.