Unwanted Parameter Value Prompts

[Dwight]

I have a report that is based on a parameter query. There are actually 3 queries and the parameters are in the first but the report gets its fields from the 3rd query.

When a user clicks on the report a dialog box Form opens so they can enter the parameters. Everything works as designed but there is an annoying glitch.

About 25% of the time when the user clicks the report prompts for parameters pop up. Since there are multiple queries and the parameters are in the first there are a lot of prompts. If you click cancel they go away and then the form will open and it will work fine. But this frightens the users.

How do I get rid of these unwanted prompts? It is in Access 2002.

Thanks,

 

[Vassago]

Use a form for the parameters instead. The queries will always look for the parameters on as long as it's not equal to anyting. If you have the parameter entered on a form, then they will always equal something, even if that something is null. Then they won't get the parameter pop-ups if nothing needs to be entered in those fields. Get it?

Let me know if I can help more,

Vassago

 

[Vassago]

Looks like you beat me Pat! I should know better than to try and beat you to the punch huh?

 

[Dwight]

2 similar answers. They are probably dead on but I'm a still a little confused.

The queries do get the criteria from a form (I hope). In the query's criteria field it has an expression like: Form! Between (Start Date) and (End Date) and then there is another one to enter the client. It is a crosstab and then there are two select queries that do some arithmetic to get the fields organized for the reports.

I have a macro (I do not know VB) that opens a form when the users click on the report. The form allows them to enter the criteria but sometimes it seems like the program gets ahead of itself and these little boxes "Enter Parameter Value" show up. If you cancel them they go away and the form opens. Then you can enter the parameters and the queries and report goes.

Pat, you answered something like this before. I will try to find the thread. You said there was leftover code in the report.

Thanks,

 

[Dwight]

I found the problem. I had a field called "Date" which of course is a reserved word. I changed that and now it seems to be firing on all cylinders.

Thanks for the advice.