Wrox Home  
Search P2P Archive for: Go

  Return to Index  

access thread: Re: The search key was not found in any record


Message #1 by "Rory" <mcneillr@c...> on Fri, 30 Nov 2001 03:34:06
> I am trying to update a record and I am receiving the message "The 

search 

> key was not found in any record."  It is only one field that is giving 

> this problem and the field only gives the problem in that specific 

> record.  The field is a foreign key to a look up table and the number is 

> one of the IDs in the look up table.  I am using Access XP.  I looked in 

> the help files and found the below explanation.

> 

> The search key was not found in any record. (Error 3709)

> This error occurs when an ISAM SEEK is being executed and there are no 

> matching values in the index.

> 

> I am not sure I understand this explanation.  Moreover, this is not the 

> first time data has been updated in this table and there are many copies 

> of this database being used by my client that have never gotten this 

> error.  Why is this cropping up?  Does anyone have any idea what is 

> causing it?

> 

> Thanks,

> Yehuda
Message #2 by "Pamela Bengtson" <pamb@r...> on Fri, 30 Nov 2001 20:30:03
> > I am trying to update a record and I am receiving the message "The 

> search 

> > key was not found in any record."  It is only one field that is giving 

> > this problem and the field only gives the problem in that specific 

> > record.  The field is a foreign key to a look up table and the number 

is 

> > one of the IDs in the look up table.  I am using Access XP.  I looked 

in 

> > the help files and found the below explanation.

> > 

> > The search key was not found in any record. (Error 3709)

> > This error occurs when an ISAM SEEK is being executed and there are no 

> > matching values in the index.

> > 

> > I am not sure I understand this explanation.  Moreover, this is not 

the 

> > first time data has been updated in this table and there are many 

copies 

> > of this database being used by my client that have never gotten this 

> > error.  Why is this cropping up?  Does anyone have any idea what is 

> > causing it?

> > 

> > Thanks,

> > Yehuda
Message #3 by "Pamela Bengtson" <pamb@r...> on Fri, 30 Nov 2001 20:34:19
Hi -



I recently had the same error show up in Access 2000.....I also could not 

find a reasonable explanation, however, when I did a compact and repair on 

the database, the record was then able to be updated without receiving the 

error.



Pam




  Return to Index