Re: Unwanted Parameters Show Up ina Report

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If Access cannot match a name to a field, it assumes it must be a parameter.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Robert T" <RobertT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:954D464E-84AC-4045-A1E1-4E6A7F7FDE4B@xxxxxxxxxxxxxxxx
Hello Allen:

Thank you so much for your response, you were right on the money. I
checked
the Sorting/Grouping and I was grouping on a field called [YR] which I had
changed to [YEAR]. When I made that change, the parameters box no longer
showed up.

What's the relationship between referencing an incorrect field and the
Parameters dialog box showing up?

Thanks,
RT

"Allen Browne" wrote:

In report design view, open the Sorting and Grouping dialog (View menu),
and
have a peek there.

Then open the Properties dialog (View menu). Make sure you are seeing the
properties of the report (not of a text box.) On the Data tab, clear the
Filter and Order By properties, and confirm that the RecordSource is the
query you think it is.

If you are still stuck, it must be the Name or part of the ControlSource
of
a control.

Or possibly Access is confused about what a field used to be named. You
can
eliminate this possibility by unchecking the Name AutoCorrect boxes
under:
Tools | Options | General
and compacting the database.

"Robert T" <RobertT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:35D4D4A4-E9CE-4F1B-B01D-33B173B862BB@xxxxxxxxxxxxxxxx
Hello:

I had an old report wherein I changed the source and developed a new
query.
The query worked perfectly when it runs by itself. However, when I run
the
report, it prompts me for a year parameter. I checked everywhere and
could
not find any parameters in the query. As I said before, the query works
perfectly outside of the report.

I then built a new report using the same exact query and it worked
flawlessly without any parameters popping up. That told me the
parameter
issue was with the report. Where do I look to find that annoying
parameter
and how can I get rid of it?


.

Relevant Pages

  • Re: Problem with Send Object
    ... Inserted into criteria of report query: ... How are you passing that filter string to the report, ... Allen Browne - Microsoft MVP. ...
    (microsoft.public.access.formscoding)
  • Re: Working with many-to-many relationships
    ... You can now use the function in a query, just like the built-in functions such as Trimor Left. ... Allen Browne - Microsoft MVP. ... it would be best to get it working in a query, and then base the report on ... >>> The titles are in a table, the authors are in a table ...
    (microsoft.public.access.reports)
  • Re: Reports, Subreports & VBA
    ... Then create a new query, ... Allen Browne - Microsoft MVP. ... >> it should give the right results when the main report calls it. ... >>> In the example of your SQL Statement, ...
    (microsoft.public.access.reports)
  • Re: "0.0" Value (not Null)... missing value in report
    ... When you view the query results directly, ... Now open the report in design view. ... Allen Browne - Microsoft MVP. ... 'CalculationChecker' report but produces a blank on my application report ...
    (microsoft.public.access.reports)
  • Re: Report with date range selection
    ... you do need one query. ... Allen Browne - Microsoft MVP. ... Then use this query as the record source for the report. ...
    (microsoft.public.access.reports)