By Passing Parameter query

[bearcub]

I have a field that keeps on popping up when I run a report that behaves like a parameter query (where you have enter in the text box the value you want displayed). However, I don't have a parameter query running in my query in that field. It looks like phanthom parameter query. I redid the report and query but I'm getting the same results. Do you know what could cause this to happen?

thank you for your help,

Michael

 

[alansidman]

I suspect that you have designated a field in your query that does not exist in the table you are querying. Double check all the fields in your query to make sure you don't have a random orphan.

 

[Micron]

Run the query for the report. If it doesn't prompt but you get the prompt when you open the report, the problem is on the report. In that case, a control probably references a field that doesn't exist in the query (could be just a spelling error) or you may have renamed a query field after creating the report. Or you have a calculated control in the report and the expression was typed in but references a field that doesn't exist.

If you do get the prompt when running the query alone, then as noted, the query may contain a field that doesn't exist in a table. More likely, you have a calculated field in the query and the expression has the same problem as I noted above for the report.

 

[bearcub]

I'm not at work but I think the prompt only came up when I ran the report, not the query. I do recall I had a control with that name but I think I renamed it or deleted it all together. I'll have to check the controls more thoroughly next week.

Is there a macro that would prevent this prompt from occurring - like it this prompt shows up, ignore it? is there a VBA object or property that could be called to if this happens by pass it?

Thank you for your help,

Michael

 

[Micron]

Is there a macro that would prevent this prompt from occurring - like it this prompt shows up, ignore it? is there a VBA object or property that could be called to if this happens by pass it?

I think not. First of all, it's not an error, and errors are what you're able to suppress or handle differently. This is a prompt for what Access treats as a parameter that can't be resolved. Even if there was such a thing, it would often be a bad idea. If it were a parameter and you didn't respond to it because you suppressed the request for input, the null or empty string (not sure which) that you'd pass would result in no records in most (all?) cases. What you're asking for is a way to ignore a flaw in the report design, which is highly unconventional, IMHO.

You will probably find that the control is misnamed (since you say the query runs fine by itself) rather than is missing. If it were missing, there'd be a field returned by the query which simply isn't being used by the report, which is fine - unless as noted previously, a calculated control on the report references the missing or misnamed control.

 

[bearcub]

Thank you- that makes sense. I look at the controls again and find out where it started. If I can't find it, Ill just rebuild the report and sees what happens.