[AccessD] LDBView

DWUTKA at marlow.com DWUTKA at marlow.com
Fri Jun 30 10:51:44 CDT 2006


Ya, I have the Msldbuser code too, LDBview does 'work' on Access 2000 (and
it uses the same code), it just reads the wrong bits as far as corruption
goes... I find it hard to believe that the suspect flag isn't being set.  

Drew

-----Original Message-----
From: Kenneth Ismert [mailto:kismert at sbcglobal.net]
Sent: Friday, June 30, 2006 9:38 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] LDBView



Drew,

> LDBView worked fine with a 97 .mdb. I could always tell who 
> corrupted a database...

My code will connect to CORRUPT A2K databases and give you the user
list -- ADO can't. But my code uses the ADO method, too ... a good way
to verify that the dll is working.

Msldbuser.dll is essentially a dll version of LDBView. It allows you to
get the exact same information as LDBView.

But, on A2K, I have NEVER seen the suspect flag set, even though my
code reports it for both the Msldbuser.dll and ADO methods. 

That makes me think Jet 4 LDB's don't use the A97 suspect flag, if two
methods of querying the LDB never show it set. 

Anyway, if you want the code, you can have it. It will very likely work
on A2003 unmodified.

-Ken

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