Search Key Not Found

[Guest]

Hello,

I am using Access 2000, I have a table with about 75000 records, linked to a
couple of other tables by the primary key. I am getting an error when I try
and change certain fields.

The name, address telephone fields I can change no problem. There is a field
that is a flag or a status field, it is normaly empty but if someone has
asked for something a signle charecter is entered and the database picks up
on that. Such as information would be an 'i', registration would be an 'r'
etc. When I try and edit that field, programicaly or manualy, it comes up
with an error "Search key not found in any record"

I have looked on various forums and they say if it is a large memo field
that has an index it could cause problems, however, this is a text field
limited to 1 in size, it is indexed though.

In the past when this has happend I had to duplicate the record and make the
old one inactive, as I could not delete it for the same errror message. But
now it is happening more often 3 times in one week.

What is going on here? Has anyone else had this problem?

 

[Guest]

I'm thinking that it's a corruption issue. At times like this, nothing beats
a good backup. In fact make a complete backup of your database now and put
it away for safe keeping.

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[Tony Toews [MVP]]

When I try and edit that field, programicaly or manualy, it comes up
with an error "Search key not found in any record"

Usually sign of corruption. Jerry has posted some good links.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

Usually sign of corruption. Jerry has posted some good links.

But sometimes a sign of a mismatched workgroup file.

 

[Tony Toews [MVP]]

But sometimes a sign of a mismatched workgroup file.

Oh, I didn't know that. Mismatched how? Just the wrong one
completely?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

Oh, I didn't know that. Mismatched how? Just the wrong one
completely?

I had this happen at a client a couple of times when they had a
generic System.MDW and a non-generic one. They both had exactly the
same default permissions, and if I used the generic one, I got
SEARCH KEY NOT FOUND but if I used the non-generic one, it didn't
happen. The data files were not corrupted in any way.

However, this may have been before Jet 4 SP6.

I couldn't figure out why the workgroup file mattered, but it
triggered that error pretty reliably if I opened the file using the
generic workgroup file.

(by non-generic, I just mean a workgroup file that had new groups
and users added to it, not one created with the security wizard)