Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments
Solved
"Data type mismatch in criteria expression", just by JOIN'ing to another table
Posted on 2013-05-14
Hello, I have two tables, say "tblParents" and "tblChildren" (Access 2010). They both have primary keys that are AutoNumber fields (say "ParentKey" and "ChildKey"). tblChildren carries ParentKey field as a Number, Long Integer.
There is a Relationship defined that LEFT JOIN's tblParents!ParentKey to tblChildren!ParentKey, as One-To-Many, all 3 options checked for Ref Integrity, Cascading Updates & Deletes.
I can start with a query with just tblChildren, printing most of the fields, for all records. No problems. But when I add tblParents to the query, and the JOIN is automatically created from the Relationship, I get the "Data type mismatch in criteria expression" error message, even if I don't throw down any fields from tblParents.
I have checked for missing or bad values in the key fields in both tables, and checked for orphans in tblChildren. Everything seems ok.
Any ideas?
There is a Relationship defined that LEFT JOIN's tblParents!ParentKey to tblChildren!ParentKey, as One-To-Many, all 3 options checked for Ref Integrity, Cascading Updates & Deletes.
I can start with a query with just tblChildren, printing most of the fields, for all records. No problems. But when I add tblParents to the query, and the JOIN is automatically created from the Relationship, I get the "Data type mismatch in criteria expression" error message, even if I don't throw down any fields from tblParents.
I have checked for missing or bad values in the key fields in both tables, and checked for orphans in tblChildren. Everything seems ok.
Any ideas?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
2
- +1
5 Comments
Active today
Did you post the exact syntax you have tried in your query?
You need to use periods, not exclamation marks:
..... LEFT JOIN .... ON tblParents.ParentKey = tblChildren.ParentKey
If that is not the problem, then do you have any corrupted records in either table where the PK field might have been messed up?
Try Compact/Repairing your database.
You need to use periods, not exclamation marks:
..... LEFT JOIN .... ON tblParents.ParentKey = tblChildren.ParentKey
If that is not the problem, then do you have any corrupted records in either table where the PK field might have been messed up?
Try Compact/Repairing your database.
Active today
Also, for kicks - try sorting tblChildren by ParentID.
Does that reveal any blanks/nulls in the ParentID field? These may cause an error in your JOINs.
Does that reveal any blanks/nulls in the ParentID field? These may cause an error in your JOINs.
ok, I was filtering on a date field in tblChildren, which I was wrapping with DateValue() to get rid of the time component on some records, and that worked fine, until I JOIN'ed to tblParents, which had some parent records with no children, as it turns out...
"WHERE DateValue(tblChildren!Chil
The filtering on the expression that assumed a value in the date field was what was causing the error message, when it hit the nulls.
I reversed the lay-out of the query, LEFT JOIN'ing tblChildren to tblParents, and that side-steps the "childless" parent records.
Thank you for your responses
"WHERE DateValue(tblChildren!Chil
The filtering on the expression that assumed a value in the date field was what was causing the error message, when it hit the nulls.
I reversed the lay-out of the query, LEFT JOIN'ing tblChildren to tblParents, and that side-steps the "childless" parent records.
Thank you for your responses
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening. This article shows how to create and use them.
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
In Microsoft Access, learn the trick to repeating sub-report headings at the top of each page.
The problem with sub-reports and headings:
Add a dummy group to the sub report using the expression =1:
Set the “Repeat Section” property of the dummy…
Suggested Courses
Course of the Month11 days, 11 hours left to enroll
730 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.