Well, I got this error message today while I was trying to import a text file:
“The search key was not found in any record”
After some research, I found that either it was a bug caused by Microsoft Jet 4.0 Service Pack or it was the size of the database (should be not greater than 2GB). It turned out to be the later one. I fixed this problem by compacting and resizing the database. In Access 2007, you click on the Office Button (Top Left Corner), then Manage > Compact and Repair Database.
For a year i have been wondering how to resolve this error until today after reading your blog.
Thank you a million!
Irene, I am glad to hear that.
thanks! this error has been a problem
I got the same problem but it was not to do with the Jet SP. I had leading spaces in column headers which I removed and was able to import.
Thanks man. Sometimes these microsoft operation system and applications come very close to driving me insane. Your recommending works well. It would be good if Microsoft help was more interactive and usefull. I’ve lost a day or more with this problem. cheers for being a saviour
Not a problem, clement. I am glad that these solutions helped you.
For me is not working I try your suggestion still not working…
Made all different attepmts not work….
Thanks, really helped.
They should make the error message more useful, though. Something like “Hey, your database is too big.”
Thanks from my side too,
Error message was really insane!
Hi i’m was looking for this solution for an emergencyy with a database in my job THANKSSSSS
I have not be able to fix this problem, I have been trying to split my database, and come with this error, am using Access 2007. Note that I am using Office 2007 with SP2.
Wonderful!!! i had benn fighting with this problem the last year.
Thanks man you have solved one of the more famous problem leading with data base.
Im not used to write something in this kind of blog,s but in this case… amazing
I never thought that the solution were so easy.
nice, thanks
Thanks! I had a leading space in a column header as well.
Thanks. I have been dealing with with problems for over a year and it was solved by this post. Thanks again.
Thanks all! After reading here, compacting the database allowed me to run a Make Table query that was previously showing the same cryptic error message. I was working with 1,269,183 records. In terms of bad error messages: Programmers, can’t live with ’em, can’t live without ’em!
Thanks, this is very informative forum. It really help me alot with with this problem.
Worked for me. For a long time, I was trying to figure out how to resolve this issue.
thanks a bunch!!!.
Thanks! The Compact DB worked perfectly. Classis Microsoft white-tower programmer nonsense. I wonder how many thousans of man-hours it would save to say either:
“Column Headings need to be trimmed” OR
“Please compact your database first (top left > Manage Database)”
Seriously?
Thanks for the heads-up here though.
Error msgs need to be more Meaningful…thats for MICROSOFT…Hey thanks a lot for the solution!!!
Thank you!
If compacting the Database does not work and u are getting this msg trying to import a csv file, just be sure the source file has no empty titles.
I truly wish that the developers would right a little better descriptive error codes. Your tip was a true life saver…
Thank you very much!
WM
An error occured
We won’t tell you where or why
Lazy Programmers
I am having the search key error also. No leading spaces, Have compacted and repaired a few time.
How many characters can be in a heading.
Like Sean I also had leading spaces in two of the column headers in my original Excel file. Once I deleted these, the file imported.
I have to say a7n9…I greatly appreciate your post. It saved me on today! Its working like a charm now!!!! Thanks
Yay! Add me to the list of satisfied readers! I got this error when trying to delete one specific record from a table. ‘Compact & repair’ fixed it!
I get the same message “The search key was not found in any record” when importing a text file into Access 2003. I tried compacting the database, removing leading spaces from header record and the problem still occurs. Can anyone help.
Diana, I’m sorry you are still facing the same problem. Let’s see if anybody else has any solution. I’ll keep searching too.
Thanks for this – I’ve looked at loads of sites this morning trying to find out what this error means, and this one is the only one I’ve found with an actual suggestion of how it may be fixed! I’m compacting/repairing right now… fingers crossed!
My issue was resolved when I refreshed my links to my split database. Error gone!
Refreshing the linked tables did the trick for me.
Compact & Repair Database resolved the issue for me. The “search key not found” appeared when I attempted to import Excel and text files of 150k+ lines (23,770kb). Once I ran the C&R, my files loaded with no problem.
Thanks for your assistance.