Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-access > #11928 > unrolled thread

Recurring 'search key not found' Errors

Back to article view | Back to comp.databases.ms-access

Contents

  Recurring 'search key not found' Errors Neil <xxx@gmail.com> - 2016-07-19 03:32 -0500
    Re: Recurring 'search key not found' Errors Patrick Finucane <patrickfinucanetx@gmail.com> - 2016-07-19 04:10 -0700
      Re: Recurring 'search key not found' Errors Neil <xxx@gmail.com> - 2016-07-19 18:20 -0500

#11928 — Recurring 'search key not found' Errors

We keep getting the dreaded 'search key not found in any record' error 
in one of our databases. This database has been in use for years. But 
only in the past few months did it start getting this error. Doing a 
compact on the back end resolves the error. But then it pops up again a 
week or two later in a different record.

We have two other, similar, databases, that don't have this problem 
(they have different users). But this database, for some reason, keeps 
having this problem.

About 10 days ago, I completely rebuilt the front and back ends of the 
database. I started with brand new ACCDB files (Access 2010).

In the back end I created new tables from scratch. I then copied and 
pasted the fields in table Design view from the old tables into the new 
ones. I then manually recreated the indexes. Then I linked the old data 
into the new back end (creating a second set of table objects), and used 
append queries to append the data to the new tables, and then deleted 
the table links. I then recreated the table relationships.

In the front end, I imported all the objects from the old front end, and 
then recreated the table links (didn't import the table links).

I thought that would resolve the problem. But it's still happening.

Any ideas what might be causing this, and what I can do to try and 
resolve it?

Thanks!

[toc] | [next] | [standalone]

#11929

On Tuesday, July 19, 2016 at 4:33:13 AM UTC-4, Neil wrote:
> We keep getting the dreaded 'search key not found in any record' error 
> in one of our databases. This database has been in use for years. But 
> only in the past few months did it start getting this error. Doing a 
> compact on the back end resolves the error. But then it pops up again a 
> week or two later in a different record.
> 
> We have two other, similar, databases, that don't have this problem 
> (they have different users). But this database, for some reason, keeps 
> having this problem.
> 
> About 10 days ago, I completely rebuilt the front and back ends of the 
> database. I started with brand new ACCDB files (Access 2010).
> 
> In the back end I created new tables from scratch. I then copied and 
> pasted the fields in table Design view from the old tables into the new 
> ones. I then manually recreated the indexes. Then I linked the old data 
> into the new back end (creating a second set of table objects), and used 
> append queries to append the data to the new tables, and then deleted 
> the table links. I then recreated the table relationships.
> 
> In the front end, I imported all the objects from the old front end, and 
> then recreated the table links (didn't import the table links).
> 
> I thought that would resolve the problem. But it's still happening.
> 
> Any ideas what might be causing this, and what I can do to try and 
> resolve it?
> 
> Thanks!

I could have a faulty brain.  Are your tables getting fed data from Excel?  i think I may have had this error from an Excel import long long ago...just don't hold me to it.

I would be looking at any changes on the adding of records if it is failing on new records

[toc] | [prev] | [next] | [standalone]

#11934

On 7/19/2016 6:10 AM, Patrick Finucane wrote:
> On Tuesday, July 19, 2016 at 4:33:13 AM UTC-4, Neil wrote:
>> We keep getting the dreaded 'search key not found in any record' error
>> in one of our databases. This database has been in use for years. But
>> only in the past few months did it start getting this error. Doing a
>> compact on the back end resolves the error. But then it pops up again a
>> week or two later in a different record.
>>
>> We have two other, similar, databases, that don't have this problem
>> (they have different users). But this database, for some reason, keeps
>> having this problem.
>>
>> About 10 days ago, I completely rebuilt the front and back ends of the
>> database. I started with brand new ACCDB files (Access 2010).
>>
>> In the back end I created new tables from scratch. I then copied and
>> pasted the fields in table Design view from the old tables into the new
>> ones. I then manually recreated the indexes. Then I linked the old data
>> into the new back end (creating a second set of table objects), and used
>> append queries to append the data to the new tables, and then deleted
>> the table links. I then recreated the table relationships.
>>
>> In the front end, I imported all the objects from the old front end, and
>> then recreated the table links (didn't import the table links).
>>
>> I thought that would resolve the problem. But it's still happening.
>>
>> Any ideas what might be causing this, and what I can do to try and
>> resolve it?
>>
>> Thanks!
>
> I could have a faulty brain.  Are your tables getting fed data from Excel?  i think I may have had this error from an Excel import long long ago...just don't hold me to it.
>
> I would be looking at any changes on the adding of records if it is failing on new records
>

Thanks, yeah, I think they do do some importing from Excel (in addition 
to manually entering records). That very well could be what changed in 
the past few months. Thanks!

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.ms-access

csiph-web