The search key was not found in any record
Hello experts. I inherited a front end ms access application which connects to a sql database. One of my forms it connects to a sql table called tbl_conversations. The table has no primary or foreign keys (if that matters). Here is my issue. I added a new column to the table (tbl_conversations) called track. I then re-open ms access and when I attempt to update the table in the linked table manager I received a message that says "The search key was not found in any record". I select ok and naturally I cannot see the field I want to add as a record source on the form. I tried a compact and repair and still no luck. Any ideas on how to resolve would be great.
Did you ReLink the SQL table to your front end after you added the new field ?
ASKER
Jim, there are no system name and no spaces in front. Also this was not created in access 2000
Joe, per my question when I try to re-link the table via the linked table manger I receive the message. Are you referring to something different?
Joe, per my question when I try to re-link the table via the linked table manger I receive the message. Are you referring to something different?
There are any number of problems that can cause this (for example, with A2002 see the below MSKB).
So a little more info then; what version is this? What data type is Track? etc.
Jim.
==========================
ACC2002: "Run-Time Error '3709'" Error Message When You Enter a Large Amount of Text in a Memo Field That Contains an Index
The information in this article applies to:
Microsoft Access 2002
This article was previously published under Q302525
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access database (.mdb).
SYMPTOMS
When you create a Memo field in a Microsoft Access database and create an index on that field (or you create a field name that includes text that is automatically indexed), you can enter only a specific amount of text. Once you reach this limit (approximately 3450 characters), you can enter no more text and you can also not edit the existing data. If you try to do so, you receive the following error message:
Run-time error '3709':
The search key not found in any record. x
So a little more info then; what version is this? What data type is Track? etc.
Jim.
==========================
ACC2002: "Run-Time Error '3709'" Error Message When You Enter a Large Amount of Text in a Memo Field That Contains an Index
The information in this article applies to:
Microsoft Access 2002
This article was previously published under Q302525
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access database (.mdb).
SYMPTOMS
When you create a Memo field in a Microsoft Access database and create an index on that field (or you create a field name that includes text that is automatically indexed), you can enter only a specific amount of text. Once you reach this limit (approximately 3450 characters), you can enter no more text and you can also not edit the existing data. If you try to do so, you receive the following error message:
Run-time error '3709':
The search key not found in any record. x
ASKER
Version of access is 2016 32 bit (16.0.4639.1000). Data type for field "Track" will be a drop down box (nvarchar(255), null)
Something has to be wrong with the field name or the data type.
Have there been any other changes to that table?
Jim.
Have there been any other changes to that table?
Jim.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
<< I go back into my previous ms application and receive that "search key" message when attempting to re-link.>>
The form and/or DB is corrupt then.
Make sure you accept your own last comment as answer.
Jim.
The form and/or DB is corrupt then.
Make sure you accept your own last comment as answer.
Jim.
ASKER
Ok. Thanks for the help and insight
ASKER
Closing per last comment from Jim.
And if this is Access 2000, it could be due to an old bug:
https://support.microsoft.com/en-us/help/301474/bug-you-receive-a-the-search-key-was-not-found-in-any-record-error-mes
Jim.