![]() I did use a subquery but that makes the query take really long to run (there 791 expected rows returned): Lookup field wizard when designing the tables, in which case the values of the Project and/or Product tables would not be the text values you see, but a hidden numeric value. This could be the case if for instance you've used the dreaded Of course these alternative solutions don't rule out the possibility of a mismatch on the data types. If there is a possibility that the subquery could return more than one row use an arbitrary aggregation operator to force it to return a single row: WHERE tblProjects_Products.Project = qryDC-CHARt1.ProjectĪND tblProjects_Products.Product = qryDC-CHARt1.Product) AS Techny ![]() You can then include the Technology column in the SELECT clause. TblProjects_Products.Project = qryDC-CHARt1.Project AND tblProjects_Products.Product = qryDC-CHARt1.Product It might be a mismatch on the data types or the fact that you are referencing the alias Proj_ID rather than the original column name, but rather than calling the DLookup function why not just join the tblProjects_Products table to the result set of the
0 Comments
Leave a Reply. |