Does Access 'Remember' Corruption Occurred?

[Guest]

Hello all,
Here is my situation:
My client sent me a copy of the BE of our database. I made a copy of it and
I have been working in it and all is fine. After a few days I opened a table
and noticed that one of the records was corrupted. I tried to delete it but
could not. I tried compacting and repairing but that failed. It won't even
let me in. I've tried the JetComp utility but to no avail.

Finally, I went to the original copy that I saved before I made any changes,
I tried to open it thinking all would be fine and I get the same corrupt
database message! That copy was fine originally and now it has the same
problems as the one I was working in that became corrupted?

So my question is this: I tried to open a copy that was totally fine and now
just by opening it, it is flagging it as corrupted. Can anyone think of why
that would be? It is possible that the corrupted record existed in the copy
that was sent to me but all was working fine and I would have thought that I
would have had problems immediately. Any suggestion? Thanks,
Debbie

 

[Allen Browne]

Yes: it is quite possible that the file had a corruption, but you did not
come across it.

For example, if record 987 has a memo field that has gone bad, you may not
know anything about it until you try to read that record.

 

[Susie DBA [MSFT]]

ACCESS CORRUPTION IS AVOIDABLE

the answer is _NOT_ DAO
the answer is _NOT_ dotnet

JUST USE ACCESS DATA PROJECTS, KIDS

 

[Tony Toews [MVP]]

Note that this person is really A a r o n K e m p f and that he is not an employee
of Microsoft.

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

 

[Guest]

Allen and Tony,
Thanks for your reply. I undestand what you are saying but I would think
that in the older copy, the corrupted record hasn't been accessed yet so I
should at least be able to open that copy, i.e. Access hasn't 'found' the
corruption yet. The older copy does have the same name as the corrupted one
so I didn't know if that somehow 'tell's Access that this is corrupted.
Thanks,
Debbie

 

[Allen Browne]

Could there have been any changes since that time? Examples:

- A JET update?
- Other software installed?
- Crosslinked files on your drive?
- Someone else opened (and corrupted) the file?

 

[Tony Toews [MVP]]

Thanks for your reply. I undestand what you are saying but I would think
that in the older copy, the corrupted record hasn't been accessed yet so I
should at least be able to open that copy, i.e. Access hasn't 'found' the
corruption yet. The older copy does have the same name as the corrupted one
so I didn't know if that somehow 'tell's Access that this is corrupted.

No, Access looks through the file itself to see if a file is corrupted. It has no
idea about the name of the file and doesn't remember the name of the file in that
context.

As Allen stated in his original posting if you have a corrupt record or memo field it
may have happened weeks or months ago but wasn't noticed until you scrolled down the
records or did a compact and repair.

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

 

[Tony Toews [MVP]]

No, Access looks through the file itself to see if a file is corrupted.

Just to clarify that a bit. In a corrupt record/memo field situation
the problem is only found if a user somehow manages to hit that
record. So if the record is several years old and is never reviewed
or queried you may never know about it.

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

 

[Susie DBA [MSFT]]

Tony;

that sounds like a GREAT database you preach, kid

 

[Guest]

Thank you Allen and Tony,
Since there have been no updates at all, I think I'm looking at a corrupted
record that hadn't been identified. Thank you very much for explaining this
to me.
Debbie