Results 1 to 5 of 5
  1. #1
    Star Lounger
    Join Date
    Mar 2002
    Location
    Sherbrooke, Qc, Canada, Quebec, Canada
    Posts
    58
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Networked Database (Access 97)

    I have a problem with a networked database that was made using access 97.
    Basically the office where the problem is occuring is using a small WinNT Network where they store a database so that many ppl can access the database easily. The other day, 2 ppl were accessing the database and one of the person had to do a CTRL-ALT Delete to terminate the MS Access application that was frozen.
    Ever since that day, when I close any instance of the database, I get a message that "The buffer is locked by another user" even if there is only but one (1) user on the database itself.
    How could I "Unlock the buffer" so that the program works like it would normally do ?
    Is there a "buffer" file that I could delete ?

    Any help would be GREATLY appreciated <img src=/S/cheers.gif border=0 alt=cheers width=30 height=16>
    Thanks in advance

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Networked Database (Access 97)

    Is there an error message associated with the message? That helps determine where Access thinks the problem is. As a wild guess, it sounds as if the .LDB file used to store lock information is the cause. Make sure everyone is out of the database, and then check to see if there is still a file with the same name as the database, but with an extension .LDB. If such a file exists, delete it and then see if that makes the problem go away. I would also suggest two other things - compact and repair the database in question as killing Access can cause corruption, and consider splitting the database into a front-end and a back-end, and deploy the front-end out to each user's workstation. The latter will give improved performance, and less vulnerability to corruption. Hope this helps.
    Wendell

  3. #3
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: Networked Database (Access 97)

    I want to make sure you understand how important Wendell's suggestion was to split the database if you have not already done so. This generally eliminates the problem you found, plus prevents alot of corruption problems.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  4. #4
    Star Lounger
    Join Date
    Mar 2002
    Location
    Sherbrooke, Qc, Canada, Quebec, Canada
    Posts
    58
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Networked Database (Access 97)

    Actually there were 2 error messages generated.
    I don't remember the actual text of the error message but it was errors 3343 damaged database and 3276 exclusive mode.
    I did notice the LDB file and looked into it with a regular text editor and 2 usernames of the ppl using the database.
    I will try deleting the LDB file and see what it does.
    I also tried repairing the database and compacting it without success either.
    I'll also look into spliting the database, it might help prevent future problems.

    Thank you very much for your ideas on this problem
    Have a nice day now

  5. #5
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Networked Database (Access 97)

    It appears that you database is indeed corrupt, and you may want to try importing all the objects from it into a new database. One of the advantages of splitting the database is that it reduces the likihood of corruption, especially in the data (back-end) MDB file.
    Wendell

Posting Permissions

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