Enter parameter value of a field in Report.

[Georgios Eleftheriadis]

I have the following problem:
I have a report rpt_A with the text controls
-txt_Barcode,
-txt_PUNr,
-txt_SeamNr,
-txt_Description
with data source the table tbl_SeamsPrintQueue with fields

-Barcode,
-PUNr,
-SeamNr,
-Description
Then I copy and paste rpt_A to create a report rpt_B, similar to rpt_A.
The report rpt_B has as data source the table tbl_PUIPrintQueue with fields
-Barcode,
-PUNr,
-PUINr,
-Description.
After I rename the txt_SeamNr to txt_PUINr and set its control source to the field PUINr of tbl_PUIPrintQueue I run the report rpt_B.
For some reason the report is asking for the value of parameter SeamNr!
It seams that SeamNr still is the source of some control of rpt_B!
Is there any solution to this problem?
Is this a known bug of Access reports?

Thanks in advance.

 

[Gasman]

Doubt it.
Likely you have just missed something?

 

[Mark_]

You can always delete all textboxes and re-add them to make SURE you don't have a typo.

 

[DHookom]

The field could be in the Order Grouping.

 

[Georgios Eleftheriadis]

The field could be in the Order Grouping.

It was! Thanks for your time!

 

[The_Doc_Man]

You got your solution, so this is just an add-on for future consideration. Depending on how you built the report, there was another place to look. If you build a report directly from a table via a wizard that lets you pick fields from the table, it builds an SQL Select query (as a text string) and stores that as your report's .RecordSource - which means that you would have to examine and edit the .RecordSource to find the culprit. Note that this does NOT apply when you build the report directly (without using the wizard) from a named query.

 

[Georgios Eleftheriadis]

You got your solution, so this is just an add-on for future consideration. Depending on how you built the report, there was another place to look. If you build a report directly from a table via a wizard that lets you pick fields from the table, it builds an SQL Select query (as a text string) and stores that as your report's .RecordSource - which means that you would have to examine and edit the .RecordSource to find the culprit. Note that this does NOT apply when you build the report directly (without using the wizard) from a named query.

Thank you for sharing!