Record fills with foreign characters and garbage-can't delete-can't repair

[Van T. Dinh]

Tony Toews has a very comprehensive article with lots of
links to other related documents. See:

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

HTH
Van T. Dinh
MVP (Access)

 

[Van T. Dinh]

Create a new Table exactly the same as the existing Table except using Long
instead of AutoNumber for the PK. Append all *good* Records from the
existing Table including the (AutoNumber) PK Field values. Re-create the
bad Records using exactly the same old AutoNumber values.

Once, you recover / re-create all Records, go into the new Table and change
the Field from Long to AutoNumber.

 

[Tony Toews]

Create a new Table exactly the same as the existing Table except using Long
instead of AutoNumber for the PK. Append all *good* Records from the
existing Table including the (AutoNumber) PK Field values. Re-create the
bad Records using exactly the same old AutoNumber values.

Once, you recover / re-create all Records, go into the new Table and change
the Field from Long to AutoNumber.

And recreate the relationships.

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

 

[Van T. Dinh]

Sorry, I was thinking of SEED Number in MS-SQL Server.

Has the problem machine been patched with all OS & Office Service Releases /
Service Patches?

Have you scanned the problem machine for virus?

I have also seen one case where a faulty SIM card did weird things to the
database which I didn't work out until I replace the SIM card and the
problem disappeared.