Beverly,

     

       I've had similar problems.  I use 'svrmgr.exe' (found in the the 

     WinNT Resource Kit) to display all connected users to the Shared 

     folder containing the database.  This allows me to see which machine 

     is connected to the share and allows me to disconnect theem.  The 

     'filename.ldb' file will also inform you of who has the database open.

     Although I cannot open the .ldb file directly, I have been successful 

     in copying it and opening the duplicate in Notepad.

     

     Unfortunately, I have not discovered how this situation occurs.  The 

     user tells me that they are no longer connected.





______________________________ Reply Separator _________________________________

Subject: (access) RE: Access File Locking

Author:  "Beverley Usher" <SMTP:bUsher@h...> at SOIGATEWAY

Date:    03/20/2001 3:00 AM





Access 97 files on one of my servers are locking themselves down. All of 

the files have been working well in a multi-user environment (and the 

same files on three other servers are fine), but on one server, a file 

will suddenly insist that it is in use and cannot be used by anyone 

else. This is true even early in the morning when no one is at the site. 

Even as supervisor/owner of the files, I cannot delete them or change 

their name, or delete the directory they are in. The only work-around I 

have found so far is to rename the entire directory, create a new one 

and put new copies of the files there. The directory I had to recreate 

this morning is 700 MB so I really do not want to have to do this much 

longer.

     

Has anyone had a similar problem? Does anyone have any ideas of how to 

solve this or of better work-arounds?

     

Any and all help appreciated.

     

Beverly

Jetutils.exe (available here: 

http://download.microsoft.com/download/access97/utility1/1/WIN

98/EN-US/JETUTILS.EXE) contains useful stuff for sorting out 

problems like these. Along with a white paper that explains 

exactly what Access does when it locks a record \ database, 

there's an lbd file viewer which tells you who is still 

connected to the database and what state the database is in.



BDS



---- Original message ----

>Date: Tue, 20 Mar 2001 08:03:00 -0500

>From: "WISE, MICHAEL" <MMWISE@s...>

>Subject: [access] RE: (access) RE: Access File Locking

>To: "Access" <access@p...>

>

>     Beverly,

>     

>       I've had similar problems.  I use 'svrmgr.exe' (found 

in the the 

>     WinNT Resource Kit) to display all connected users to 

the Shared 

>     folder containing the database.  This allows me to see 

which machine 

>     is connected to the share and allows me to disconnect 

theem.  The 

>     'filename.ldb' file will also inform you of who has the 

database open.

>     Although I cannot open the .ldb file directly, I have 

been successful 

>     in copying it and opening the duplicate in Notepad.

>     

>     Unfortunately, I have not discovered how this situation 

occurs.  The 

>     user tells me that they are no longer connected.

>

>

>______________________________ Reply Separator 

_________________________________

>Subject: (access) RE: Access File Locking

>Author:  "Beverley Usher" <SMTP:bUsher@h...> 

at SOIGATEWAY

>Date:    03/20/2001 3:00 AM

>

>

>Access 97 files on one of my servers are locking themselves 

down. All of 

>the files have been working well in a multi-user environment 

(and the 

>same files on three other servers are fine), but on one 

server, a file 

>will suddenly insist that it is in use and cannot be used by 

anyone 

>else. This is true even early in the morning when no one is 

at the site. 

>Even as supervisor/owner of the files, I cannot delete them 

or change 

>their name, or delete the directory they are in. The only 

work-around I 

>have found so far is to rename the entire directory, create 

a new one 

>and put new copies of the files there. The directory I had 

to recreate 

>this morning is 700 MB so I really do not want to have to do 

this much 

>longer.

>     

>Has anyone had a similar problem? Does anyone have any ideas 

of how to 

>solve this or of better work-arounds?

>     

>Any and all help appreciated.

>     

>Beverly