[AccessD] Reading an .ldb File

Jim Dettman jimdettman at verizon.net
Thu Apr 10 06:51:02 CDT 2008


Dan,

  The problem with looking at the LDB directly is that your only seeing part
of the picture.

  The two other pieces of the puzzle are the locks being held on the .LDB
file itself and the commit bytes in the database header page.

  You'll find many of the users listed in the .ldb file don't are not in the
database currently.  Also, if user level security is not used, every user
name will be "Admin".

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Thursday, April 10, 2008 7:34 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Reading an .ldb File

I've used this for a few years - it works well when the system can be gotten
into!

Making a copy of the .ldb file and changing it to a text file is something
that my non-technical customer can do quickly and effectively when they want
to try to solve the problem themselves.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Wednesday, April 09, 2008 11:26 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Reading an .ldb File


And http://support.microsoft.com/kb/198755/EN-US/

On 10 Apr 2008 at 12:29, Darren D wrote:

> Check out
> 
> http://support.microsoft.com/kb/186304
> 
> haven't tested it though
>  
> Darren
> -----------------
> T: 1300 301 731
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
> Sent: Thursday, 10 April 2008 4:48 AM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Reading an .ldb File
> 
> Just for FYI:
> 
> This morning I was working with a customer where someone had opened a
> database which we needed to close, but we didn't have way of finding out
who
> had opened it.  Out of frustration, I made a copy of the .ldb file,
changed
> the .ldb to .txt, and opened the file.  Lo and Behold - the user names and
> computer names of the logged in users were displayed.  
> 
> Interestingly, it appears that the first person who logs in has their user
> displayed as Admin, not their actual user name.  But because the computer
> name was correct, we were able to figure out who it was and get him to
close
> his instance of Access.
> 
> The computer names and user names are all in the first row of text, so you
> may want to hit the Enter key a few times for better readability.
> 
> Perhaps this would be useful...!
> Dan
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list