Corrupted Record

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a record that suddenly changed all the dates to 12:00am and most of
the entries into what looks like Japanese. The unique ID should be 154, but
instead it's turned into "-1577058149". I tried to delete the record and
re-enter, but when I highlight and ask it to delete (from the table) is says
"The search key was not found in any record." and won't let me.
How do I get rid of this record?
Thank you in advance for your help.
Gee...
 
Import all the db objects into a new, blank database. The corrupted record
shouldn't be able to tag along (if Access can't delete it, it won't be able
to import it either). Delete the old database (or rename it and save as a
backup...)

If your database is replicated, check your replicas carefully. That record
won't be corrupted in replicas but I've found that synchronizations have
been significantly impaired since the corrupted record came into existence
(i.e., after synchronization, the db with the corrupted record shows 100
records changed for a given day but all others show only 50.) I actually use
a comparison of changed record counts to call my attention to possible
record corruption issues ASAP. Compacting failures is another red flag.

Prevention is another story.
 
I have a record that suddenly changed all the dates to 12:00am and most of
the entries into what looks like Japanese. The unique ID should be 154, but
instead it's turned into "-1577058149". I tried to delete the record and
re-enter, but when I highlight and ask it to delete (from the table) is says
"The search key was not found in any record." and won't let me.
How do I get rid of this record?
Thank you in advance for your help.
Gee...
Click to expand...

You'll probably need to take some serious action to fix this. See Tony
Toews' Corruption FAQ at

http://www.granite.ab.ca/access/corruptmdbs.htm

I'd suggest creating a new, empty .mdb file; import everything *but*
this table; import this table *design mode only*. Then link to it and
run an Append query appending only the non-corrupted records (use a
criterion on the Primary Key field so it uses only the Index, not a
table scan) to append the good data. This record is toast and will
need to be manually reentered; any records which were related to it
will need to be checked.

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps
 
I made a duplicate of the whole database and the record was still there, and
weird, but I was able to delete it! It worked perfectly...thanks!
 
Back
Top