Hi, thanks for coming back to me. I think the question I am really asking is has access been changed/update really. I have never had an issue with these query types before, and it works perfectly with a normal join. I also tested it by creating a table of the data for one of the queries instead and again the query worked perfectly.
multipart bound errors normally relate to issues with he joins or access tot he fields - but as this is drag and drop and I have edited nothing it make no sense to me that it can fail. Especially when the table works fine with the same data.
query one pull out all the items of a type
SELECT feature.id, feature.type
FROM feature
WHERE (((feature.type)='001'
query two finds any items on the lists to be checked
SELECT feature.id, inspection_route.type
FROM
(insp_route_feat INNER JOIN inspection_route
ON insp_route_feat.insp_route_code = inspection_route.insp_route_code)
INNER JOIN feature
ON (insp_route_feat.plot_number = feature.plot_number) AND (insp_route_feat.site_code = feature.site_code)
WHERE (((inspection_route.type)="12"));
the final query looks for anything in query 1 that is not in query 2 - or at least should
SELECT Q1.id, Q2.id, Q2.insp_route_code
FROM Q1 LEFT JOIN Q2 ON Q1.id = Q2.id;
If I run it with an inner join to find all matched records as below it runs fine and shows me each item and the route it is checked on
SELECT Q1.id, Q2.id, Q2.insp_route_code
FROM Q1 INNER JOIN Q2 ON Q1.id = Q2.id;
I have had to anonymise the sql due to the data but this is the SQL I am using - again I have not edited this - just used access to drop in the tables and right click the join to change the properties - hence why I find it so baffling.
thanks