Microsoft Knowledge Base Email Alertz

KBAlertz.com: (244137) - No records are returned for a query that joins a Microsoft Access 2000 (Jet 4.0) table to a linked Microsoft Access 97 (Jet 3.5) table. This happens even though you are certain that there are matching records. This behavior can occur only when all...

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 244137 - Last Review: January 25, 2007 - Revision: 3.1

No records returned in query between an Access 2000 table and a linked Access 97 table

This article was previously published under Q244137
Moderate: Requires basic macro, coding, and interoperability skills.

This article applies only to a Microsoft Access database (.mdb).

On This Page

SYMPTOMS

No records are returned for a query that joins a Microsoft Access 2000 (Jet 4.0) table to a linked Microsoft Access 97 (Jet 3.5) table. This happens even though you are certain that there are matching records.

CAUSE

This behavior can occur only when all the following conditions are true:
  • The query contains an Access 2000 table and a linked Access 97 table.
  • The two tables are joined in a one-to-one relationship (Type 1).
  • In each table, the linked field has a data type of Text and is indexed.

RESOLUTION

Instead of a join, use a criteria with the keyword Like that compares one field to the other field in the linked tables. For instance, to correct the behavior in the example in the "Steps to Reproduce Behavior" section later in this article, follow these steps:
  1. Highlight the join between the two tables to select it.
  2. Press DELETE.
  3. In the Criteria field under CustomerID from the Customers table, type the following:
    Like [Customers1].[CustomerID]

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

CAUTION: If you follow the steps in this example, you modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and follow these steps on a copy of the database.

Steps to Reproduce Behavior

  1. Place an unchanged copy of the sample database Northwind.mdb that is included with Access 97 on your desktop. Do not convert it to Access 2000.
  2. In Access 2000, open the sample database Northwind.mdb that is included with Access 2000.
  3. On the File menu, point to Get External Data, and then click Link Tables
  4. In the Link dialog box, browse to the Access 97 version of the sample database Northwind.mdb, click Northwind.mdb, and then click Link.
  5. In the Link Tables dialog box, click Categories and Customers, and then click OK. Note that two new linked tables, Categories1 and Customers1, appear in the Database window.
  6. Create a new query that includes both the Customers table from the sample database Northwind.mdb 2000 and the linked Customers1 table. Note that the tables are automatically joined on the CustomerID field (Primary Key in both, and Text in both).
  7. Drag the CustomerID field from both tables to the query design grid.
  8. Run the query.

    Note that no records are returned.
  9. Create a second query that includes the Categories table from the sample database Northwind.mdb 2000 and the linked Categories1 table. Note that the tables are automatically joined on the CategoryID field (Indexed in both, and Numeric in both).
  10. Drag the CategoryID field from both tables to the query grid.
  11. Run the query.

    Note that all records are returned. In this case, because the joined fields are a Number data type instead of a Text data type, records are returned.

APPLIES TO
  • Microsoft Access 2000 Standard Edition
  • Microsoft Access 97 Standard Edition
Keywords: 
kbbug kbpending KB244137
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please