Results 1 to 7 of 7
  1. #1
    Join Date
    Sep 2011
    Posts
    19

    Unanswered: How do I fix Run-Time Error 3027?

    Good Morning,

    One of my databases is experiencing the "gremlin effect". It was working fine yesterday until this morning. For some reason the backend of my database is in a "read-only" mode. The database is not locked, and no one is in it. (except right now I am because I'm trying to figure out stuff).

    What happens is we have users who need to submit requests to a central database. The On-Click event of the submittal form opens up the backend table, and then the code adds the request to the table.

    The users who work off of this information are in a separate database. Their database is totally locked down right now. No one can type in it, alter it, etc. I can go in and alter code, but it doesn't stop the fact that no one can work on their requests right now.

    This is the code that opens the table to submit the information

    Code:
    Dim rsRequest As Object
    Set rsRequest = CurrentDb.OpenRecordset("Split-Merge - Request table")
    
    rsRequest.AddNew
    There are more lines of code after this but this is where the debugger stops it at the "rsRequest.AddNew" line, and I get the Run-Time Error 3027.

    Any ideas as to how I'm supposed to unlock this table that doesn't appear to be locked?

    Thanks bunches!!
    Ari

  2. #2
    Join Date
    Mar 2009
    Posts
    5,442
    Provided Answers: 14
    1. Backup Database (in the File Menu). This will create a new compacted database that hopefully should not be locked. Check and if it works, discard the original database and rename the backup.

    2. Compact and Repair (in the Tools Menu). This basically performs the same operations as a backup, but does not produce a new file (a temporary file is used, that is deleted at the end of the operation). I prefer the first method: I find the Compact and Repair operation a little risky.

    3. If both methods above do not work, create a new database and import all the tables from the back-end into it, check and if it works, discard the original database and rename the new database.
    Have a nice day!

  3. #3
    Join Date
    Sep 2011
    Posts
    19
    I had to do the 3rd option. My old database won't delete though, it says it's locked, but it's not. Everyone is out of the databases that are referencing it, so I don't know. I created a new database, gave it a similar name, and make all the tables reference that one instead.

    Thanks for the help!

  4. #4
    Join Date
    Mar 2009
    Posts
    5,442
    Provided Answers: 14
    You're welcome!
    Have a nice day!

  5. #5
    Join Date
    Aug 2003
    Location
    Cleveland USA
    Posts
    184
    I've had a similar problem. There are a couple of free utilities out there that reads the .ldb file and tells you who's in it.

    What you're describing can happen if someone exited badly, such as their computer crashing. If you knew who the person was, having them go back in and then exiting nicely can fix the problem. If you only have a handful of users, then you can have them all close out, reopen, then close again to reset the ldb.

  6. #6
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    If all else fails, rebooting the server will unlock it too.
    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

  7. #7
    Join Date
    Jun 2005
    Location
    Richmond, Virginia USA
    Posts
    2,763
    Provided Answers: 19
    As will a relatively small block of C-4!
    Hope this helps!

    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

Posting Permissions

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