Occasionally my MS Access reports:
The search key was not found in any record
After this happens the solution is to close Access, compact and repair the backend and then delete the record.
What causes this and how can I avoid it?
views:
3613answers:
5
A:
It sounds like you might have a corrupt database. One way you might be able to identify the source (especially if its something in the application portion of it) is to use the no-so-documented /decompile command it (make a backup firs of course); and then recompile it in the VBA side using the Debug->Compile command.
From there, it would be a matter or replacing the corrupt object (form/report/module).
CodeSlave
2008-10-16 03:02:11
The "Search Key Not Found" is a Jet error, i.e., data-related. Decompile is VBA-related (i.e., *not* Jet-related), so decompiling won't have any effect whatsoever on a data error.
David-W-Fenton
2008-10-19 15:53:18
A:
Another possible cause of this error is a mismatched workgroup file. That is, if you try to use a secured (or partially-secured) MDB with a workgroup file other than the one used to secure it, you can trigger the error (I've seen it myself, years ago with Access 2000).
David-W-Fenton
2008-10-19 15:54:41
A:
In Access 2007 this error occurs when importing an Excel file where there are two fields with the same column header.
bfox
2010-08-26 14:17:17
Er, no, it doesn't happen in that circumstance -- I just tested (with the wizard and with TransferSpreadsheet) and it imports it just like it did in earlier versions of Access, providing a unique name for the duplicate column. It may be that this error *also* happens sometimes when importing, but it's independent of having duplicate column headers in the source spreadsheet.
David-W-Fenton
2010-08-27 02:59:38