I have several linked "tables" to dBase III+ files called
Moe.dbf and moecust.dbf.
I set a relation based on a common key called cust_code.
I can create a query to each table indivually with no
problem. However, when I try to create a query using
both linked "tables" I get a message "The search Key was
not found in any record".
I have gotten the latest Service patches to both Windows
XP Pro and Windows 2000.
I am running Acces 2000 and Access 2002 on my XP Pro
machine and I get the same message. I also get the
message on a machine running Windows 2000 (with all
current SP's installed) running Access 2000.
I have installed 282010 Hot fix as called out in
KnowlegeBase article 282010.
This could be related to the registry key;
1. In the Registry Editor, browse to the following Registry key:
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Xbase
2. On the Right Pane, Click on Deleted.
3. Right-Click on the Deleted and click on Modify.
4. Change the entry from
0000 01
to
0000 00
4. Click OK.
5. Close the Registry and then open Access and run the query.
In addition, the message indicates that Microsoft Access cannot view the
indexes on theDBase table, are you able to link to other DBase files and
run it correctly? If other dbase files work fine, I suspect that you will
need to troubleshoot the structure of the DBase table. The following
articles may be of help. When you troubleshoot your DBase file, please try
to make sure that there is a single index on each of the tables. You will
need to contact DBase support if you have any questions on how to change an
index in DBase.
You might also check to make sure that there is a corresponding index file
in the same directory as the DBase file you are linking to. The following
extensions indicate index files for dBase: .ldx, .cdx, .ndx, or .mdx.
ACC: Index Missing for Attached FoxPro or dBASE Table ID: Q122561
http://support.microsoft.com/support/kb/articles/Q122/5/61.ASP
Here is another article that may help us troubleshoot the index issue:
ACC: dBASE Unique Index Does Not Behave as Expected ID: Q163279
http://support.microsoft.com/support/kb/articles/Q163/2/79.ASP
Another method we can try is:
1. Import the Dbase table to a new blank Microsoft Access database.
2. Export the table as a DBase III file.
3. In your original Microsoft Access 2000 database, delete the link to the
DBase file.
4. Relink to the DBase file you created in Step 2.
What happens when you try the above?
Let's try it again and do the following: Before exporting the DBase table
from
Microsoft Access, open the table in design view. Select the View menu and
click on Indexes.
Check to make sure there are no combined indexes. You will know if there
is a combined index if there are entries in the Field Name column with no
corresponding entries in the Index name column. Remove any combined
indexes and then export the table.
Please feel free to reply to the threads if you have any questions.
Sincerely,
Alick Ye, MCSD
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "BJ Perry" <b...@krlbantry.com>
| Sender: "BJ Perry" <b...@krlbantry.com>
| X-Tomcat-NG: microsoft.public.access.queries