[AccessD] LDBView

DWUTKA at marlow.com DWUTKA at marlow.com
Thu Jun 29 10:49:58 CDT 2006


I can read the locks, I even know WHERE the locks are.  The problem I still
have to check is the bytes representing the users are different from 97, so
I have to figure out what represents a regular lock, and what represents a
suspect user.

Drew

-----Original Message-----
From: Jim Dettman [mailto:jimdettman at earthlink.net] 
Sent: Thursday, June 29, 2006 9:59 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] LDBView

Drew,

<<Does anyone have something like LDBView for 2000 (or newer) databases?>>

  Your SOL; there is no such animal.\

<<Everything I have found on
Google so far points to an MSKB article which has code to get a schema
through ADO, to see who is in a database.>>

  That's it as far as I know. 

<<I am about halfway through creating a new LDBView, but it's involving a
lot
of guess work and reverse engineering.  Getting a little tired of walking up
hill with this, so if anyone has something prebuilt, it would be much
appreciated!>>

  Difficult at best because you also need to read the locks associated with
the login from the OS.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DWUTKA at marlow.com
Sent: Thursday, June 29, 2006 10:25 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] LDBView

Does anyone have something like LDBView for 2000 (or newer) databases?  We
recently converted from Office 97 to Office 2003, and have a few of our
databases (even very stable ones) get corrupted several times in the last
week and a half.  LDBView would tell me who corrupted a 97 database, but it
doesn't work correctly with Access 2000 and up.  Everything I have found on
Google so far points to an MSKB article which has code to get a schema
through ADO, to see who is in a database.  That's all well and good, but it
doesn't work if the db is corrupt, because it can't connect to it.  I even
created an app that stayed 'in' the database, and when it went corrupt, the
code from MS didn't show who corrupted it.

 

I am about halfway through creating a new LDBView, but it's involving a lot
of guess work and reverse engineering.  Getting a little tired of walking up
hill with this, so if anyone has something prebuilt, it would be much
appreciated!

 

Drew

-- 
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