So, occasionally we get the "search key not found in any record" error (error 3709). This usually happens when a particular field in a form is updated, and the record is attempted to be saved.
The assumption was that there was a corruption in the back end. So we do a Compact and Repair on the back end, and that clears up the problem. However, today I noticed something strange.
I went into the back end table that had this issue, and edited the field that usually causes the error and then tried saving the record. As expected, I got the error.
However, I then edited a different field in the same table record and was able save the record! So the corruption apparently was limited to that one field, which doesn't make a lot of sense to me, because I thought the entire data page would be corrupted.
As noted, this was done in the back end table, so there was no VBA code coming into play. There was no data macro either. Just a straight field being edited, nothing more.
I checked the table that it was related to, and in particular the record in the related table that it currently was using, and that table was fine. Was able to edit and save it.
The field in question is a Long Integer field, Required = Yes, Indexed = Yes (Duplicates OK).
It's related to a lookup table on the lookup table's PK field, which is an autonumber. Enforce Referential Integrity is enabled. Cascade Update and Cascade Delete are disabled.
Any thoughts as to why this error would be happening only with this particular field in the table record, and no other fields in the same record?
Version = Access 365.
Thanks!
The assumption was that there was a corruption in the back end. So we do a Compact and Repair on the back end, and that clears up the problem. However, today I noticed something strange.
I went into the back end table that had this issue, and edited the field that usually causes the error and then tried saving the record. As expected, I got the error.
However, I then edited a different field in the same table record and was able save the record! So the corruption apparently was limited to that one field, which doesn't make a lot of sense to me, because I thought the entire data page would be corrupted.
As noted, this was done in the back end table, so there was no VBA code coming into play. There was no data macro either. Just a straight field being edited, nothing more.
I checked the table that it was related to, and in particular the record in the related table that it currently was using, and that table was fine. Was able to edit and save it.
The field in question is a Long Integer field, Required = Yes, Indexed = Yes (Duplicates OK).
It's related to a lookup table on the lookup table's PK field, which is an autonumber. Enforce Referential Integrity is enabled. Cascade Update and Cascade Delete are disabled.
Any thoughts as to why this error would be happening only with this particular field in the table record, and no other fields in the same record?
Version = Access 365.
Thanks!