>>>>What is the exact difference between two?
>>>
>>>>I do need to set order for SQL-Select using OLD style indexes (IDX). That was discussed recently on UT and Hugo R helped me to understand that. For these tables we're using old style IDX indexes.
>>>
>>>I think you need to SET INDEX TO to open the .idx so it can be used for Rushmore. I can't prove that at this moment.
>>>
>>>I'm pretty sure you don't need SET ORDER.
>>
>>Let me try without, but I'm not yet sure it's relevant. E.g. with or without order it should still produce the correct result, what do you think? When why I got two wrong invoices listed as mismatch and why I can not reproduce the problem in the command window for the mismatched invoices, but do receive exactly the same two invoices as wrong. I really can not understand what's going on.
>
>What if the .idx file wasn't updated? The query may pull the correct result, but the seek and sum while won't.

True, but as I said, the Inv_No and Salesman fields are not touched in this procedure and somehow Select SUM gets two records where in one case the salesman in the table is different than passed value and in the other case the inv-no doesn't exist at all. When I run these selects in the command window they produce no results. That's why it's very strange.