I tried your suggestion with different variations but had errors.. (Sorry).. Maybe its a Access Sql quirk.

Here is the final Query I came up with which works perfectly..It may not be the ideal coding practices.. I was a Cobol Programmer.. SQL very rusty.

Regards Mark

FROM ( SELECT pickerid, currentdate, pickerhours, pickername, SUM(currentweight) AS totalweight FROM mergeddatabase GROUP BY pickerid, currentdate, pickerhours, pickername ) AS [%$##@_Alias]

 
That’s your table expression for the FROM clause. You have “AS” in order to apply an alias name. I’m just going to call the name MyAlias. So, the basic structure is simply FROM (MyAlias).
 
You have parentheses to mark the beginning and end of that part of your query.
 
The first thing that seems odd to me is that you whole query has a WHERE clause, but the conditions only seem to apply to your table expression. The conditions don’t seem to be totally relevant to your final outer query. To me, it would all seem better if you had things looking like this:

FROM ( SELECT pickerid, currentdate, pickerhours, pickername, SUM(currentweight) AS totalweight FROM mergeddatabase GROUP BY pickerid, currentdate, pickerhours, pickername WHERE ((currentdate between [Enter first date:] AND [Enter last date:]) and (pickerhours > 0.1)) ) AS [%$##@_Alias]

 Hmmm… it’s going to be a mess no matter how I do it.
 
But the WHERE clause is moved up to be part of your table expression instead of being applied to the final query. That is, I moved it inside those parentheses.
 
It’s possible that Access will do that as part of some optimization. It’s also possible that it can’t be done like that because of the parameters for the dates. But it’s the way that it looks like you want things to run.
 
The only place that currentdate is used is inside the table expression. If you only want dates within a range, then they probably should be dropped before putting rows through any summarization and grouping.
 
The (pickerhours > 0.1) part is questionable, though. Do you want to select original rows greater than (0.1) or sums greater than (0.1)? That part might move back to a WHERE clause for the final query.
 
Now, this piece – ROUND(SUM(pickerhours)) .
 
You have that in your final query. You’re also using pickerhours in the GROUP BY in your table expression, which doesn’t make full sense to me. I can’t see why you want to “group” by that column. I would more expect that to be a SUM() value instead of a GROUP BY. You might have a reason, so I can’t say that it’s wrong. It just seems odd.
 
I looked at your past history. You seem to be coding valid business queries rather than just being a student. I can help with SQL, though Access can be a little different. There are others who can tune whatever we come up with.
 
Look over my comments and see if they are readable and make sense. If we get a solid basic query first, changes will be easier to fix next. Ask questions here if explanations are needed.
 
Tom