Database Corruption

[Guest]

I have been experiencing a lot of BE corruption recently. Usually, a compact
and repair fixes the problem but occassionally it doesn't.

The latest one found today had a table with a Null record, even the primary
key field. I didn't think Access would allow a Null in a primary key
field...how could this happen?

I checked some recent backups and this Null record is present in all backups
going back 7 days. Compact and repair has been run on this BE during the last
week (or so I am told) but it didn't pick up this anomaly.

I do intend to check everything that Allen Browne has mentioned on his site.

Many thanks for your input.

 

[Tony Toews [MVP]]

I have been experiencing a lot of BE corruption recently. Usually, a compact
and repair fixes the problem but occassionally it doesn't.

The latest one found today had a table with a Null record, even the primary
key field. I didn't think Access would allow a Null in a primary key
field...how could this happen?

Corruption. Are there any other data fields with data present on that
record or are they all null and/or 0?

I checked some recent backups and this Null record is present in all backups
going back 7 days. Compact and repair has been run on this BE during the last
week (or so I am told) but it didn't pick up this anomaly.

No, I can see how Access/Jet wouldn't necessarily pick up this
problem.

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's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Guest]

Hi Tony.
Thanks for the reply.

Corruption. Are there any other data fields with data present on that
record or are they all null and/or 0?

A couple of fields had default values. All others were Null even the primary
key field.
There was another row that had ### or #Error in all the fields. This was not
present in the backups and I was able to delete the one offending row and
import the table. I couldn't import it before deleting the row because it
reported something about an error in a .dll and trying to assign a Null to a
Variant that wasn't of the Variant data type.

The data in this table is entered/modified in a subform. The subform does
have the primary key field (hidden) and is not linked to the parent using
this field.

Steve