Japanese characters in table

[Guest]

I have several records that show Japanese characters in some of the fields of
some records. As I scroll down through the table to view the records, Access
closes.

If I try to delete the record, it tells me "the search key was not found in
any record."

Help! What's going on here?

 

[Allen Browne]

The symptoms indicate a corruption of the mdb.

You will need to create a new (blank) table with the same struture, and them
import the good records *without* refering to any of the bad ones. The 3rd
and 4th symptoms in this article explain how:
Recovering from corruption
at:
http://allenbrowne.com/ser-47.html

 

[Guest]

Allen,

The fields showing garbage are 'text' not 'memo'...does that make a
difference on how I go about fixing the corruption?

Any suggestions on how to avoid this in the future?

 

[Guest]

Allen -

I copied the table and pasted structure only. There are 3 records that seem
to be corrupt - the primary key is Idea Number, so on the 'append' query, I
excluded those 3 numbers. But it says "invalid argument" and won't complete
the query.

Any suggestions on the next thing to try? Do I need to totally recreate the
table from scratch instead of copying?

 

[Guest]

My apologies...there ARE 2 memo fields, but there are other text fields as
well that appear to be corrupt.

 

[Allen Browne]

You could probably get away with copying the existing table "structure
only".

Make sure you don't refer to the bad numbers. For example, if row 1000 is
bad, limit your append query to:
<= 999
If the record is quite narrow (not many characters if you sum the field
sizes), you may even need to use a lower number, such as:
<= 995

Once you get that working, you can try appending the records between there
and the next problem. For example, if ID 1445 is bad, use:
Between 1001 And 1444

It can take some patience and experimentation to get this working. Allow for
the page size. Work in a copy of the database. In the copy, remove any
indexes that are not needed on the table.

Presumably you have already tried the Compact And Repair on a *copy* of the
mdb.

 

[Guest]

I too have experienced this problem. I have searched Microsoft for any
solution wirhout success. I would like to know how this corruption occurs so
that I can avoid it happening again. I can still access the corrupted records
and Autonumber/Number/Date fields appear to be intact. Perhaps the problem is
related to Unicode representation of text fields.