A lot of times when I see my data being off by a certain multiple, then I look at the underlying data in the tables. It is often the case where you are thinking it is a one to one relationship and it is really a one to many relationship. In fact, this just happened to a co-worker yesterday in her report and she couldn't figure it out. So I had her do a SELECT DISTINCT from the child table and this cleared up the problem.

You need to put the SQL directly into your database and see what the results are. Since you were able to reduce it from 20 down to 2, then that implies that this is still a join issue. I would plug the SQL into the database and get it working there before doing anything else. Also, I see that you have 10 grouping fields. That's a lot of fields to group on and I can see where it would be easy to have a dup in there causing problems and you totally miss it b/c of all the grouping. I see this problem a lot and its almost always an issue of fixing the SQL statement to get clean data. Do it in the database with the raw SQL statement so you don't have CR mucking things up.

Glad to help! Links are always appreciated.