Results 1 to 4 of 4
  1. #1
    dunc723 is offline Novice
    Windows 7 32bit Access 2010 32bit
    Join Date
    May 2013
    Posts
    27

    Record-level Locking is locking other records

    Hi,



    I have a multi-user database (about six users), split with the back end on a network server, front end on each user's machine. Only one form is used by most users. Occasionally User 1 will be editing a record, and when User 2 tries to edit a different record, gets an error message that the record is locked. As soon as User 1 saves the record, the other record is unlocked.

    The form is set for Record Locks = Edited Record. Default Record Locking = Edited Record and "Open databases by using record-level locking" = True in both FE and BE.

    Running Access 2016, 2007-2016 file format.

    Any suggestions?

    Thanks,

    Pete

  2. #2
    NTC is offline VIP
    Windows 10 Access 2013
    Join Date
    Nov 2009
    Posts
    2,392
    change the form property to: No Locks

    the lock management will be adequately managed by the back end file.

  3. #3
    Missinglinq's Avatar
    Missinglinq is offline VIP
    Windows 7 64bit Access 2007
    Join Date
    May 2012
    Location
    Richmond (Virginia, not North Yorkshire!)
    Posts
    2,923
    I agree! I twenty years I've never found the need to apply locking.

    Linq ;0)>
    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

  4. #4
    Micron is online now Virtually Inert Person
    Windows 10 Access 2016
    Join Date
    Jun 2014
    Location
    Ontario, Canada
    Posts
    6,852
    Open databases by using record-level locking"
    But what is the "Default Record Level Locking" Option in Client Settings? You might have "all records" selected.
    Seems like you are getting page level locking regardless (2Kb DAO 3.5; 4Kb DAO 4.0 I believe). If you are really concerned about those cryptic messages when 2 or more users try to edit the same record, then you might have to resort to code. I haven't done this, so I don't know if the Dirty property extends to subsequent users who navigate to a record that someone else might be editing. One way I've read to check the state of a record is to attempt rs.Edit, rs.MoveNext, then rs.MovePrevious on a form's recordset clone. Not sure why the moves are done, or if that was a continuous or datasheet type of form. I said "might" because if there are record selectors, the locked symbol appears, does it not?
    - "doesn't work" doesn't help. Implement changes in copies of your database.
    "Everyone has a photographic memory; some just don't have film." Steven Wright

Please reply to this thread with any new information or opinions.

Similar Threads

  1. record-level locking clarification
    By vientito in forum Access
    Replies: 3
    Last Post: 11-12-2014, 09:39 AM
  2. Help! Locking records
    By jlgray0127 in forum Forms
    Replies: 1
    Last Post: 05-02-2014, 06:56 AM
  3. Locking a record
    By aytee111 in forum Access
    Replies: 3
    Last Post: 04-24-2012, 05:31 PM
  4. Replies: 3
    Last Post: 11-10-2011, 03:54 PM
  5. Record Locking
    By jlclark4 in forum Database Design
    Replies: 10
    Last Post: 06-15-2011, 02:22 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Tech Forums: Microsoft Office Forums