Comparing two queries yields one result too many

Question

I have a problem that I'm pretty sure is resident in the
structure of a loop, but I'm not quite sure how to fix it.
All of this is being done within a cfc. The cfc calls the
first method for Query1, then calls the second method for Query2.
Query1 has 173 records, Query2 has 117 records. Technically the
difference should be 56 records.
However, the result of myquery (below) is giving me 57
records. And every one of them is a real record. Code as follows:
<CFSET myquery = QueryNew("var1, var2, var3, var4,
var5")>
<CFLOOP INDEX="i" FROM="1" TO="#Query1.recordcount#">
<CFQUERY NAME="checkJob" DBTYPE="query">
SELECT var1
FROM Query2
WHERE var1 = <cfqueryparam cfsqltype="cf_sql_varchar"
value="#Query1.var1
#">
</CFQUERY>
<CFIF checkJob.recordcount lte 0>
<cfset newRow = QueryAddRow(myQuery, 1)>
<cfset temp = QuerySetCell(myQuery, "var1",
Query1.var1)>
<cfset temp = QuerySetCell(myQuery, "var2", Query1.var2
)>
<cfset temp = QuerySetCell(myQuery, "var3",
Query1.var3)>
<cfset temp = QuerySetCell(myQuery, "var4", Query1.var4
)>
<cfset temp = QuerySetCell(myQuery, "var5",
Query1.var5)>
</CFIF>
</CFLOOP>
<CFRETURN myQuery>
So if all is done correctly, I should be getting the results
from Query1 that are NOT in Query2.
It's *almost* right.
Since var1 exists in all of the records returned by myquery,
one presumes that there's an extra record being returned that *IS*
in Query2.
I'm not sure why, though.
The resultant screen needs to print out all of the variables
from query1 that do not exist in query2. Hence, myquery.
Anyone have a better recommendation on how to fix this
problem? I feel like a goober for even asking it, but it's been
annoying me all afternoon.
Rizados

Answer 1

Simon, I would appreciate not being called lazy and yet
overly complicated in the same sentence. Ignorant, perhaps, overly
complicated, very likely, but lazy isn't the word I'd use.
When it comes to MSSQL, I was actually unaware I could use a
query of queries approximation without writing the whole thing out.
Thank you so much for correcting my ignorance. My apologies if this
isn't the type of database I've been using for the last few years,
and if my familiarity with the database is not as great as yours.
I have been trying to componentize this application where
applicable, and the queries I speak of were already componentized
prior to me coming into this. Both the primary and secondary
queries are being used by multiple applications on the same server,
and multiple times in the same page with different parameters (the
same page is being used several times). This third query is
obviously the difference between the two. If the second query has
to change at any time, then changing it only once within a
component makes more sense than having to find it multiple times
within the code to change it again, since the business rules on
said query have had to change a few times before. Better to have it
in one place than to change it in multiple places and risk having
one be changed while the others are not.
Lazy has nothing to do with it so much as accuracy. Multiple
instances of the same code means having to find it multiple times
when the code needs to change, and risking that you may miss one.
If they allowed me to use a view to do it as recommended by
cf_dev2, I would do so, and it would make my life a lot less
complicated. However, that option is not available to me, therefore
I have to go the "more complicated" route.