intersect and access 2000

[madison]

I know Intersect is not supported on access 2000 so i was wondering what
will be the alternative in access 2000 for the following query:





SELECT Language.LanguageName, Area.AreaNAme

FROM [Language] INNER JOIN Area ON Language.LanguageID = Area.LanguageID

WHERE (((Area.AreaNAme)="InterfaceData"))

intersect

SELECT Language.LanguageName, Area.AreaNAme

FROM [Language] INNER JOIN Area ON Language.LanguageID = Area.LanguageID

WHERE (((Area.AreaNAme)="InterfaceUser"))

intersect;

 

[MacDermott]

I'm not familiar with "intersect" in this sense; in a mathematical sense it
would usually mean that both criteria should be true, but obviously
Area.AreaNAme can't be both "InterfaceData" and "InterfaceUser", so the
intersection of these two recordsets would always be null.

If you want to create a recordset where one of the two criteria is met, you
could use UNION between the two SELECT statements (drop "intersect" at the
end), which would produce a non-updatable query.

Or you could structure your WHERE clause like this:
WHERE (((Area.AreaNAme) IN ("InterfaceData","Interface User")))
using a single SELECT statement.
This will produce an updatable query.

HTH
- Turtle