The search key was not found in any record in Access

1. Irene
   March 7, 2010 at 7:37 am | Permalink

   For a year i have been wondering how to resolve this error until today after reading your blog.

   Thank you a million!

2. a7n9
   March 8, 2010 at 8:47 am | Permalink

   Irene, I am glad to hear that.

3. Carla
   March 19, 2010 at 10:39 am | Permalink

   thanks! this error has been a problem

4. Sean
   June 25, 2010 at 8:16 am | Permalink

   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.

5. clement
   July 5, 2010 at 8:21 am | Permalink

   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

6. a7n9
   July 6, 2010 at 8:11 am | Permalink

   Not a problem, clement. I am glad that these solutions helped you.

7. Val
   August 5, 2010 at 9:42 am | Permalink

   For me is not working I try your suggestion still not working…
   Made all different attepmts not work….

8. Adam
   August 23, 2010 at 3:16 pm | Permalink

   Thanks, really helped.

   They should make the error message more useful, though. Something like “Hey, your database is too big.”

9. Jordi
   October 4, 2010 at 5:00 am | Permalink

   Thanks from my side too,
   Error message was really insane!

10. NELLY
    October 14, 2010 at 9:42 am | Permalink

    Hi i’m was looking for this solution for an emergencyy with a database in my job THANKSSSSS

11. Karo
    October 20, 2010 at 2:12 am | Permalink

    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.

12. jose alberto
    January 14, 2011 at 11:39 am | Permalink

    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.

13. jasbir
    March 3, 2011 at 4:10 am | Permalink

    nice, thanks

14. bob mac
    March 9, 2011 at 12:15 pm | Permalink

    Thanks! I had a leading space in a column header as well.

15. Mo
    March 14, 2011 at 4:08 pm | Permalink

    Thanks. I have been dealing with with problems for over a year and it was solved by this post. Thanks again.

16. David Lindsey
    April 1, 2011 at 9:50 am | Permalink

    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!

17. Ralph G.C.
    April 26, 2011 at 11:03 pm | Permalink

    Thanks, this is very informative forum. It really help me alot with with this problem.

18. navvi25
    September 2, 2011 at 9:33 am | Permalink

    Worked for me. For a long time, I was trying to figure out how to resolve this issue.
    thanks a bunch!!!.

19. Michael
    November 14, 2011 at 8:29 am | Permalink

    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.

20. Bharathi
    December 7, 2011 at 6:20 am | Permalink

    Error msgs need to be more Meaningful…thats for MICROSOFT…Hey thanks a lot for the solution!!!

Leave a Reply Cancel reply