Not sure why I'm being asked for a parameter.

[lccrews]

I've attached a simplified version of my database so you can see the problem I run into. I created a query to give me the sum of a number called 'qry_TheoreticalYield'. When you open the query itself, it works as expected, giving the total. However, when I added this query to a report it always asks for a parameter 'tbl_Formulas.Item'. Can someone tell me why? I've looked everywhere and can't figure out why it keeps asking for this. Any help would be appreciated.

[pbaldy]

Look at the Order By property of the report.

[ranman256]

Unintentional parameters mean either a field is misspelled, does not exist, or
(in reports) a group is there for a missing field.

[lccrews]

Paul,
I checked that. It's blank. I've never used it because I don't know how to use it.

Ranman,
Thanks, I'll look into this and report back.

[pbaldy]

When I open the report in design view, the Order By property contains:

[tbl_Formulas].[Item]

If you don't see it, try putting focus there and deleting the contents. Also set the Order By On Load to No.

[lccrews]

Paul, I have checked for [tbl_Formulas].[Item] in so many places. I don't know why I didn't see this. It's correct now and functions properly. I'll always wonder why that happened. Thanks Paul.

[pbaldy]

No problem, glad it works for you now.

[dslomer64]

I was constantly being asked for "Query2.Circuit". I *HAD* a query named "Query2" but deleted it with no errors. I have a field named "Circuit" in tables "AtTheBox" and "Outlets" and in my query named "WattsWhere". No misspelling, field does exist (query doesn't), and I had no reports. So much for your answer, y'know? Short general answers solve few mysteries in my experience.

[pbaldy]

I was constantly being asked for "Query2.Circuit". I *HAD* a query named "Query2" but deleted it with no errors. I have a field named "Circuit" in tables "AtTheBox" and "Outlets" and in my query named "WattsWhere". No misspelling, field does exist (query doesn't), and I had no reports. So much for your answer, y'know? Short general answers solve few mysteries in my experience.

That sounds more like criticism than a question. If so, it's misplaced and frankly inappropriate.

[Micron]

It's unwarranted as well. OP of this thread posted a database which helps cut out a lot of questions and enables a short (and in this case, accurate) answer. There should be no expectation on your part that answers to this thread will apply to a solution for your problem, which I have already tried to contribute to.