Record Locking on a Split Database - Access 2010

Question

Hey guys,

I have a split Access 2010 database with around 8 users who each have a local frontend copy of the database, with the backend residing in my network drive.  Only three users actually enter data, while the other 5 just use the database to run reports.  My question lies in what to do about record locking.  Right now, all my forms are set to No Locking via their property sheet.  But even still, users can get locked out of the database, I believe because of the laccdb?

I'll admit my users only have read/write access.  I am working with IT to give the read/write/create/delete because that what I have read is best for multi user use with no collisions.  But provided that they are granted those permissions, what should I do about the record locking property? 

I feel like it should be locked because I don't want users editting the same records and getting errors, but at the same time I want the best environment for simultaneous use.  Any help at all on the topic will be most appreciated.

-B

Answer 1

Record locking should not be an issue.  You shouldn't use record locking unless it is absolutely necessary (I had to implement this one time due to a program where two users FREQUENTLY could actually be editing the same record at the same time and it caused problems, but most of the time there should be no issue).

ALL users need to have read/write/delete permissions on the folder where the database backend resides.  This is so that Access can delete the laccdb file when the last user leaves.  If the last user to leave doesn't have delete permissions, then it is stuck there and can cause problems.