Self Joins in Access - Error Encountered.

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Darragh

    Self Joins in Access - Error Encountered.

    Hi all!

    I'm having a bit of an issue making a self join in access (similar to
    the example explained on Allen Browne's excellent site -
    http://allenbrowne.com/ser-06.html).

    I've made the self join in the query window, however when I've tried
    to run the query i get the message "table t1 opened exclusively by
    another user, or it is already open through the user interface and
    cannot be manipulated programmaticall y"

    Initially I thought it might be a corruption problem - but I mocked up
    a similar self join in a brand new database, and still get the same
    error.

    I am using Access 2003.

    Any help appreciated.

    Regards
    Darragh
  • Allen Browne

    #2
    Re: Self Joins in Access - Error Encountered.

    Suggestions:

    1. While Access is not running, look in the folder where you database
    resides. You should see an MDB file. If you also see a very small LDB file
    with the same name as the MDB, delete the LDB. It contains locking
    information. Access normally deletes it when you exit your database, but it
    may be left over after a crash.

    2. Make sure you have Name AutoCorrect turned off.
    Uncheck the boxes under:
    Tools | Options | General | Name AutoCorrect
    Explanation of why:
    Describes a series of bugs in Microsoft Access that occur if you do not disable the Name AutoCorrect options.

    Then compact/repair the database:
    Tools | Database Utilities | Compact/Repair

    3. Under Tools | Options, make sure you have the locking strategy set to:
    No Locks
    If you use table-level locking, you could have problems trying to use
    multiple instances.

    --
    Allen Browne - Microsoft MVP. Perth, Western Australia
    Tips for Access users - http://allenbrowne.com/tips.html
    Reply to group, rather than allenbrowne at mvps dot org.

    "Darragh" <darragh.murray @gmail.comwrote in message
    news:885bf4d3-7f87-4165-abc3-4ffe772e8d92@s1 2g2000prg.googl egroups.com...
    Hi all!
    >
    I'm having a bit of an issue making a self join in access (similar to
    the example explained on Allen Browne's excellent site -
    http://allenbrowne.com/ser-06.html).
    >
    I've made the self join in the query window, however when I've tried
    to run the query i get the message "table t1 opened exclusively by
    another user, or it is already open through the user interface and
    cannot be manipulated programmaticall y"
    >
    Initially I thought it might be a corruption problem - but I mocked up
    a similar self join in a brand new database, and still get the same
    error.
    >
    I am using Access 2003.
    >
    Any help appreciated.
    >
    Regards
    Darragh

    Comment

    • Bob Quintal

      #3
      Re: Self Joins in Access - Error Encountered.

      Darragh <darragh.murray @gmail.comwrote in
      news:885bf4d3-7f87-4165-abc3-4ffe772e8d92
      @s12g2000prg.go oglegroups.co
      m:
      Hi all!
      >
      I'm having a bit of an issue making a self join in access (similar
      to the example explained on Allen Browne's excellent site -
      http://allenbrowne.com/ser-06.html).
      >
      I've made the self join in the query window, however when I've
      tried to run the query i get the message "table t1 opened
      exclusively by another user, or it is already open through the
      user interface and cannot be manipulated programmaticall y"
      >
      Initially I thought it might be a corruption problem - but I
      mocked up a similar self join in a brand new database, and still
      get the same error.
      >
      I am using Access 2003.
      >
      Any help appreciated.
      >
      Regards
      Darragh
      Have you set Record locking to "all records"?

      --
      Bob Quintal

      PA is y I've altered my email address.

      --
      Posted via a free Usenet account from http://www.teranews.com

      Comment

      Working...