×
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.
Gotta call BS on this one, Adam <grin>. Look at my complete program
compared to what is in effect just the query in SQL. See how many times I
have to define fields or matches. With your UNION and the two JOINs,
there's a whole lot of field enumeration going on, and you still don't have
the code that identifies which records are matching, or found in only one
file. And you still haven't written the report! You still need to create a
cursor or run through a result set and print it, not exactly negligible.
Sure, we had some giggles trying to remember the exact syntax, but I
basically had the thing right (with the exception of the *IN02) from the
beginning. Compare that to the various issues we had with LEFT EXCEPTION
JOIN vs. RIGHT EXCEPTION JOIN, and I'm still thinking that the matching
records was a lot easier.
Joe
From: Adam Glauser
Wow, looks like matching records really _is_ so much easier than SQL! :P
As an Amazon Associate we earn from qualifying purchases.