Results 1 to 6 of 6
  1. #1
    jaydreese is offline Novice
    Windows 7 64bit Access 2013
    Join Date
    Jan 2015
    Posts
    3

    The table "DwgLog" is already opened exclusively by another user, or through the user interface


    I am in the middle of creating a small database [access 2013] and get the below error after I did a view of the form and clicked it [the "X" on the form], now I can't do a design view, modify, edit, add, etc.....

    I get this error:

    The table "DwgLog" is already opened exclusively by another user, or through the user interface and cannot be manipulated programmically.

    I got out of access [closed it], reopened it and still the same problem. Additionally I shut down and rebooted and still the same thing! I even saved as and created a copy basically of the database and that too has the problem...

    Any answers for this?

  2. #2
    Missinglinq's Avatar
    Missinglinq is offline VIP
    Windows 7 64bit Access 2007
    Join Date
    May 2012
    Location
    Richmond (Virginia, not North Yorkshire!)
    Posts
    3,016
    Do you, in fact, have a custom Table named DwgLog? Only references I can find to DwgLog online relates to AutoCad.

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

    All posts/responses based on Access 2003/2007

  3. #3
    jaydreese is offline Novice
    Windows 7 64bit Access 2013
    Join Date
    Jan 2015
    Posts
    3
    I just named the table I created in access "DwgLog".

  4. #4
    Missinglinq's Avatar
    Missinglinq is offline VIP
    Windows 7 64bit Access 2007
    Join Date
    May 2012
    Location
    Richmond (Virginia, not North Yorkshire!)
    Posts
    3,016
    Coincidences do happen! This type of thing comes under what I call Strange, Odd and Curious Behavior, and S/O/C/Bfrequently translates into corruption. In this case it could be corruption of the Form or, even worse, corruption of the entire database!

    At any rate, the first thing to attempt, for this type of corruption, is to create a new, blank file and import everything into it. Only takes a minute or two to create and check out, and if it doesn't work you haven't really lost anything! And, amazingly, it does frequently work!

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

    All posts/responses based on Access 2003/2007

  5. #5
    jaydreese is offline Novice
    Windows 7 64bit Access 2013
    Join Date
    Jan 2015
    Posts
    3
    THat makes alot of since --- it does act as that is the issue.

    I will give it a try and let you know -

    Thnaks for the help !!

  6. #6
    Missinglinq's Avatar
    Missinglinq is offline VIP
    Windows 7 64bit Access 2007
    Join Date
    May 2012
    Location
    Richmond (Virginia, not North Yorkshire!)
    Posts
    3,016
    Let us know how it goes! There are other things that can be done to try to recover from corruption, if that's what this is, but importing into a new file is by far the easiest, and works a remarkable number of times!

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

    All posts/responses based on Access 2003/2007

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

Similar Threads

  1. Replies: 2
    Last Post: 01-03-2014, 09:35 AM
  2. Replies: 3
    Last Post: 10-23-2013, 08:10 AM
  3. Replies: 3
    Last Post: 08-12-2012, 11:53 PM
  4. Replies: 13
    Last Post: 07-27-2011, 12:38 PM
  5. Replies: 1
    Last Post: 10-19-2009, 02:37 AM

Posting Permissions

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