Using A97 on a LAN.
Our backups usually occur at night when there is no activity with the
data mdb. Occasionally we may have a user leave their front end mde open
to the back end mdb, but no issues.
Recently we have been experiencing data corruption issues with the data
mdb. After a few years of relatively trouble-free operation we are
getting a corrupted data mdb during the business day.
We have not made significant changes to our front end mde (in any case
it has worked okay for days on end, then ..crash .. usually with a "NOT
A VALID BOOKMARK" error message from the front end mde.
When we attempt to open the data mdb we get the "Not a valid mdb -
corrupted data" message and we cannot repair or compact the file.
So back to the previous nights back up and re-enter all the data!!
We are wondering if it could be a hardware problem - it has run on the
same Compaq server class machine for three years now - dodgy network
card, ram ?? We are at a loss to understand the cause.
Also, is there a way of trapping and logging such an error so we can
tell who / where experienced it first (35 users) and so give us a clue?
Thanks in advance,
Piri
It's generally considered to be a bad idea to copy an open database, as the
copy may be in an inconsistent state.
Take a look at what Tony Toews has at
http://www.granite.ab.ca/access/corruptmdbs.htm for suggestions of what to
do to solve your corruption problem.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> Using A97 on a LAN.
> Our backups usually occur at night when there is no activity with the data
[quoted text clipped - 23 lines]
>
> Piri
Piri - 28 Nov 2005 01:21 GMT
Thanks you Doug - very informative
Will follow it through.
> It's generally considered to be a bad idea to copy an open database, as the
> copy may be in an inconsistent state.
>
> Take a look at what Tony Toews has at
> http://www.granite.ab.ca/access/corruptmdbs.htm for suggestions of what to
> do to solve your corruption problem.