The search key was not found in any record

[BJ Perry]

Microsoft claims that the solution to the error message "The search
key was not found in any record" is to update the Jet 4.0. Many say
that the problem is a corrupt database which must be compacted. When
you try all the above and you still get the error message read on.....


I did in fact find the solution for "the search key was not found in
any record".

I am now using Win XP, but I had the problem under Win2K and have
users under Win2K importing from dbase III plus successfully using
Access 2000 and XP.

I upgraded to the Jet 4.0 as Microsoft said and had no luck, and I
left the Jet 4.0 patch on the systems to be current.

You have to go into the System registry using Start | Run | RegEdit

Then goto EDIT | Find and search
for:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Xbase]

and change the Deleted value from 1 to 0.

when you are done your values should be similar to below.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Xbase]
"win32"="C:\\WINDOWS\\System32\\msxbde40.dll"
"DbcsStr"=hex:01
"Mark"=dword:00000000
"Date"="MDY"
"Exact"=hex:00
"Deleted"=hex:00
"Century"=hex:00
"CollatingSequence"="Ascii"
"DataCodePage"="OEM"
"NetworkAccess"=hex:01
"PageTimeout"=dword:00000258

NOTE: Before you perform any changes in the registry you should back
it up. You can do this by performing the following steps:

1) Make sure your cursor in before the first character on the first
line.

2) Goto FILE | Export ( usually name the file using YYYYMMDD for
example 20040122 ).

3) Perform the changes listed above.

Good luck,


If you need help you can reach me at: 603.668.3215 Ext. 15 8-5 EST

or e-mail me at (e-mail address removed). Please flag your message as
important so it will stand out from the SPAM I've been getting lately.

Best regards,


BJ Perry

 

[Mike]

I am currently using W2K and Access2K and have been running into this
problem for over a week. I have tried removing the multiple indexes,
upgrading to Jet 4.0 SP8, compacting/repairing the database, as well
as your registry fix below - but none of have resolved the issue. The
database will be fine for a day or two, and then all of a sudden a few
corrupt records will apear. As of now, I've been exporting the
information, removing the corrupted records, and placing them back
into a table, but this is getting old. Would you happen to have any
other ideas on how I could prevent this from happening? Any help is
greatly appreciated - thanks.

Mike