General Question

[mapat]

Hello,

I have a general question. My users lately have been getting this "Recordset locking" message from Access. We have between 8 to 10 users using the same DB concurrently (the back-end is on a server, and the front-end is locally on their PC). I know that when certain amount of users log on to the same ACCESS db concurrently, then ACCESS will start giving problems. Would the message my users are getting be related to this? Also, if I move all the tables (back-end) to a SQL Server but keep the same ACCESS 2007 front-end locally, would this solve the "amount of users" problem and therefore make the system more reliable?

Thank you very much

 

[gemma-the-husky]

have you implemented record-locking at all?

the access default is no record locking, and this is generally sufficient - it doesnt really mean no record locking, it really means something called optimistic record locking - which asusmes there will be no problems, but if access finds one - then it lets you know.

if you have implemented record locking, then you have to be careful, as someone can open a file (locked) go to lunch, and thereby lock all the other users out. In these cases, you have to try and restrict the actual locking period to the minimum possible time to avoid such lock outs. (which is what the optimistic locking does for you, incidentally)

what exact message do you get? the "record locked by another user" can often be caused by a coding error, not a real locking error.