You seem to have negative values in your table that you want to filter out, but this is not how you do in an aggregate query.  Your method only checks if the *total sum* is greater than zero, which it always is in your case.  So your method includes all the negative values in your sum as well, and that's why you get a lower sum, 653 instead of 776.  You need to check for positive values *before* the sum function is performed.

In the query designer, instead of writing:

     Quantity
     Sum
     >0

write this:

     IIf([Quantity] < 0, 0, [Quantity])
     Sum

Then each and every row of data will go through the IIf() function before it is being summed, and all the negative values will be treated as zeroes, essentially ignored.

The actual SQL statement should clarify this as well.  Your initial method has something like this:

     HAVING Sum( ... ) > 0

indicating it is the total sum that is being check for positivity.

But my method has this:

     Sum(IIf([Quantity] < 0, 0, [Quantity]))

Kevin, thanks for your help. I wasn't able to get the iif to work--but what you said about filtering out the negative quantities gave me the idea to add a where condition to the query. "Where [Quantity]>0" is working. I assumed that if I had a query that had the correct totals--then grouping it would also give me the correct totals. I learned something new. I hope I remember it always. Here is the SQL.

SELECT tblPilingInventory.Job, [Size] & [length] AS RID, tblPilingInventory.Size, tblPilingInventory.Length, Sum(tblPilingInventory.Quantity) AS Received
FROM tblPilingInventory
WHERE (((tblPilingInventory.Quantity)>0))
GROUP BY tblPilingInventory.Job, [Size] & [length], tblPilingInventory.Size, tblPilingInventory.Length
HAVING (((tblPilingInventory.Job)="c1187"))
ORDER BY tblPilingInventory.Job, tblPilingInventory.Size, tblPilingInventory.Length;