weird characters in record

[Guest]

One record in one table of my database has chinese looking characters (could
be Japanese / Korean, etc - I can't tell the difference). I am in the UK and
all records were previously in English. This record cannot be deleted,
altered etc, so I cannot correct it back to what it was (there are about 20
plus fields to the record).

Error message:

"The search key is not found in any record" (this happens when trying to
update the record to correct it)


Questions:

What circumstances could cause this?
What is the best strategy to correct this?
How can it be avoided in future?

 

[Guest]

Those characters mean that your record has been corrupted.

Try this fix:
Under Tools > Database Utilities, select "Compact and Repair".
After the repair completes, you should be able to go to that table, click on
the bad record and delete it.

I haven't found any way to restore a corrupted record; I just have to
re-enter the
info in it.

Party on, dude.

Possible causes:
a) You don't have the latest patches installed
b) You are running it on a network VIA TCP/ IP, and the network dropped out
while you were on that record (Try another protocol such as NetBeui; It
has better stability, and you can run it right on top of TCP/IP).
c) Another program (or virus?) is running on your system that is making
Access angry. Try running it by itself.

 

[Guest]

Thanks for the info Charlie. Actually, the database is compacted and repaired
upon every exit via code. So I don't think that's it. But, I'll put your
possible causes to our IT guy and see what he makes of them.

Anybody else come across anything similar?

 

[Larry Daugherty]

Yes, not a rare occurrence. You'll probably have to go thru the
machinations to create a new table, copy all records up to the one
with the error. Copy all of the records beyond the error. Rename the
old table. Give the new table the proper name. Do what you can to
recover/re-enter or abandon the data in the corrupt record. If there
are related ~child records you'll have to handle that too.

HTH

 

[Guest]

TFTH

Yes, not a rare occurrence. You'll probably have to go thru the
machinations to create a new table, copy all records up to the one
with the error. Copy all of the records beyond the error. Rename the
old table. Give the new table the proper name. Do what you can to
recover/re-enter or abandon the data in the corrupt record. If there
are related ~child records you'll have to handle that too.

HTH