LDB Viewer

[Guest]

Recently at me place of employment we upgraded to Access 2003 from Access 97.
I have noticed that now when I use LDBViewer, I can not detect which work
station has caused the corruption of a database. When I view the information
all I can tell is who is in the database. With Access 97, I was able to tell
who caused the corruption. It would be nice if Microsoft could fix the
LDBViewer to work in Access 2003 as it did in Access 97.

Thanks.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-bd9f-dd373dcc96fa&dg=microsoft.public.access

 

[MacDermott]

Wish I had more details for you, but I'm pretty sure MS has other tools now;
LDB Viewer is considered outdated. A Google search on LDBView and Access
2003 (or even Access2000) will probably get you something useful.

Recently at me place of employment we upgraded to Access 2003 from Access 97.
I have noticed that now when I use LDBViewer, I can not detect which work
station has caused the corruption of a database. When I view the information
all I can tell is who is in the database. With Access 97, I was able to tell
who caused the corruption. It would be nice if Microsoft could fix the
LDBViewer to work in Access 2003 as it did in Access 97.

Thanks.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-bd9f-dd373dcc96fa&dg=microsoft.public.access

 

[Guest]

OK. So it is outdated. Does anyone know of the tools that are available to
troubleshoot a database that corrupts? I used LDB Viewer a few months ago on
an Access 97 Database and it worked perfectly. I was able to detect a PC
that was causing the database to go down. I would like to be able to do the
same on our Access 2003 databases. Any help or pointing me in the right
direction would be greatly appreciated.

Thanks in advance.

 

[Tony Toews]

OK. So it is outdated. Does anyone know of the tools that are available to
troubleshoot a database that corrupts? I used LDB Viewer a few months ago on
an Access 97 Database and it worked perfectly. I was able to detect a PC
that was causing the database to go down. I would like to be able to do the
same on our Access 2003 databases. Any help or pointing me in the right
direction would be greatly appreciated.

Determining the workstation which caused the Microsoft Access MDB
corruption
http://www.granite.ab.ca/access/corruption/workstation.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm