I've investigated and haven't found a method to run INTERSECT and MINUS procedures in MS Access. Does in whatever way exist
INTERSECT is definitely an inner join. MINUS is definitely an outer join, in which you choose just the records that do not appear in another table.
select distinct a.* from a inner join b on a.id = b.id
select distinct a.* from a left outer join b on a.id = b.id where b.id is null
Should you edit your original question and publish some sample data then a good example could be given.
EDIT: Didn't remember to include within the distinct towards the queries.
INTERSECT isn't an INNER JOIN. They are different. An INNER JOIN provides you with duplicate rows in instances where INTERSECT Won't. You will get equivalent results by:
SELECT DISTINCT a.* FROM a INNER JOIN b on a.PK = b.PK
Observe that PK should be the main key column or posts. If there's no PK up for grabs (BAD!), you have to write it like so:
SELECT DISTINCT a.* FROM a INNER JOIN b ON a.Col1 = b.Col1 AND a.Col2 = b.Col2 AND a.Col3 = b.Col3 ...
With MINUS, that you can do exactly the same factor, however with a LEFT JOIN, along with a WHERE condition checking for null on a single of table b's non-nullable posts (ideally the main key).
SELECT DISTINCT a.* FROM a LEFT JOIN b on a.PK = b.PK WHERE b.PK IS NULL
Which should get it done.
They are carried out by JOINs. The traditional way :)
For INTERSECT, you should use an INNER JOIN. Pretty straightforward. Simply need to make use of a GROUP BY or DISTINCT for those who have do not have a pure one-to-one relationship happening. Otherwise, as others had pointed out, you will get more results than you'd expect.
For MINUS, use a LEFT JOIN and employ the Where you can limit it so you are only returning rows out of your primary table that do not possess a complement the LEFT Became a member of table.
Regrettably MINUS isn't supported in MS Access Body workaround is always to create three queries, one using the full dataset, one which pulls the rows you need to remove, along with a third that left joins the 2 tables and just pulls records that only appear in your full dataset.
Same factor applies to INTERSECT, except you'd be doing the work with an inner join and just coming back records which exist both in.
i still got an issue with that subject: i must INTERSECT several Queries on a single Table. Which ON-Claims must i use? I can not type "ON Table.ID = Table.ID"