× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



rob@xxxxxxxxx wrote:
A join is not the same as a union.

True, but based on Richard Casey's suggestion, it looks very much like a join could be an adequate (if INSANELY verbose) stand-in for an INTERSECT:

SELECT W001.FLD1, W001.FLD2 FROM WORKFIL001 W001
JOIN WORKFIL002 W002 ON W001.FLD1 = W002.FLD1 AND W001.FLD2 = W002.FLD2 JOIN WORKFIL003 W003 ON W001.FLD1 = W003.FLD1 AND W001.FLD2 = W003.FLD2
.
.
.

The files in question are all two fields wide, with both fields in the access path.


Regarding the IN/NOT IN predicates, would that approach even work, given that I'm testing on two keyfields?

Thanks for the help you've given me so far, and thanks in advance for any further help you can provide.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.