Results 1 to 7 of 7
  1. #1
    Join Date
    Aug 2008
    Posts
    2

    Unanswered: How do I restrict only having one person in an Access DB at a time?

    I have an Access database on a network drive at work and there are about 5 people that access the db ever so often. I want to make it so only one person can open the db at a time.

    I have set the options of the db to exclusive open mode and it still lets multiple people into the database. It isn't that the db is corrupted because I tried creating a new database on a different drive and it will doesn't allow for only one person at a time.

    Do you have any ideas on how to get this to work?

    Thanks!
    J

  2. #2
    Join Date
    Mar 2007
    Posts
    277
    Why only one at a time? Is your db split to FrontEnd and BackEnd? Access is inherently multiuser.
    RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP, ac07, ac10 - WinXP Pro, Win7 Pro
    Please reply to this forum so all may learn.

  3. #3
    Join Date
    Aug 2008
    Posts
    2
    If I split the database is there something that will keep two people from overwritting a record?

  4. #4
    Join Date
    Jan 2007
    Location
    UK
    Posts
    11,434
    Provided Answers: 10
    You could opt to change the locking level on the database (see help files for more info) - without a copy of Access I can't tell you where it is, but I'm sure one of the other contributors here can follow up with the right place
    George
    Home | Blog

  5. #5
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Each form has a Record Locks property which you should have a look at.

    Quote Originally Posted by jahunt123
    If I split the database is there something that will keep two people from overwritting a record?
    Splitting the database is irrelevant to record locking. You should split a database for a whole bunch of other good reasons, but not to do with handling record locks; an Access database will handle record locks whether the database is split or not.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  6. #6
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    there is some code, which I frist saw in the Sybex Access Developer handbook which can tell you which computers and users are in a specific db, and also allow you to stop other users opening that db.. it meddles with the lock file (ldb)

    however I'd talk to the network trolls, alter the share on the db so they cannot open the file.
    I'd rather be riding on the Tiger 800 or the Norton

  7. #7
    Join Date
    Mar 2007
    Posts
    277
    I use a version of "Kick Them Off" to keep people out when I'm doing maintenance. The first thing my application does is check a value in my system table and see if they can use the system. If not then it just exits back to the OS.
    RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP, ac07, ac10 - WinXP Pro, Win7 Pro
    Please reply to this forum so all may learn.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •