Hi... I'm running a report in which I am NOT asking for parameters. The control source is the same in the report as it is in the query so I do not understand why I am still getting these parameters. I checked within the query as well and they are the same. The query is based on other queries - could that be the possible problem????

I am getting the parameters as if I need that information to be entered but the information is still coming up in the report. All I am doing is hitting 'enter' or 'okay' when Access asks for the parameter and the numbers are still showing up!!

Thank you for your help... this is driving me nuts!!!

Kimmie

Welcome to Utter Access

It does sound like the problem could be the subqueries on which the report's recordsource is based. With the report open, try opening each of the sub queries to see if one of them prompts for parameters.


HTH

George

That is exactly what is happening. Unfortunately I didn't not create any of the queries.... trying to fix this report so that it works from someone elses creation.

Why would an unexpected parameter appear in a query? I asked my boss and he did not intentionally put any parameters in any of the queries. He doesn't know how to.

I'm not quite sure how to fix this. I understand if you actually ask for a parameter... that makes sense to me and I've created that before. But I'm not quite sure why these parameters in queries are appearing. There is only one and when I hit okay or enter it still brings up all the information. If I hit the close button on the window it brings up nothing.

Thanks again....

Kimmie

Open the query which is prompting you for a parameter in design view. Look for a column which has something like "Expr1: [tblTableName].[FieldName]" It may be that the original query was created on a table which has been changed later on. If you see somethign like that, try to figure out which field in the table it should be referencing.

If that is not the case, Look at the parameter row in the query grid. You might see a reference to a form or report in one of the columns.

HTH
George

Something else you may check is the sorting and grouping window of the report. Make sure you are not trying to group by a field that is no longer in the recordsource of the report

I tried all of the above and did not find anything in the SQL view as described.

Also, one thing I noticed is that the other queries that prompt for an unexpected parameter (I did check and find this to be happening) are all union queries. Not sure if that makes a difference or not. They are asking for something that doesn't exist anywhere.... ex. Query1.sku - I have no idea what this is... there is no Query 1 (at least not called that anyway). And I think this might be some type of error... I don't think that Query1.sku is referring to an actual query but it is definitely prompting for that....

As George suggests above, you have to work back through the layers of queries until you find the one that's causing the problem.

Start with the query under the report. Go to it's SQL view and search for the string you're being prompted for. If you find it, figure out why it's there. If you don't, open each of the queries it uses and do the same thing. Kepp going- one of the queries must be the source, and once you figure out which one you should be able to fix it.

Hi Stephen,

I've actually printed out each query's SQL view.... I do not see anything resembling the original unexpected parameter or what George suggested...... and I looked in the tables as well.

That's why it's so strange - because I cannot find the original culprit anywhere and it seems that I would have to fix that in order for the rest to work correctly. It's totally driving me nuts because I did not create this..... so I'm basically creating 'in my head' what he did by backtracking.

Thx...........

Try typing a value for the parameter and see if that shows up somehwre on the report- migh provide a clue....

Thanks for the help..................we're trashing that report.... he created another one that I have to figure out now but that does not have those problems.....