deleted field - now asking for parameter of that field

[dataheadache]

I'm not sure whether this is in the right forum - but here goes....

I have deleted a field in my database called [Prog No] - but now every time I run a report it comes up with a Parameter Value box asking for the Prog No. - how do I get rid of it?

 

[___]

I'm not sure whether this is in the right forum - but here goes....

I have deleted a field in my database called [Prog No] - but now every time I run a report it comes up with a Parameter Value box asking for the Prog No. - how do I get rid of it?

Make sure you have no "Prog No." header in the report.
If you do, I think the only way is to re-create the report.

HTH

 

[spacepro]

I'm not sure whether this is in the right forum - but here goes....

I have deleted a field in my database called [Prog No] - but now every time I run a report it comes up with a Parameter Value box asking for the Prog No. - how do I get rid of it?

The field [Prog No] is referenced still in your report or the table/query that the report relates to.

Check your recordsource of the report and the report itself for the field you have deleted.

Andy

 

[dataheadache]

The field [Prog No] is referenced still in your report or the table/query that the report relates to.

Check your recordsource of the report and the report itself for the field you have deleted.

Andy

Unfortunately, it isn't. Where else could it be referenced?

 

[spacepro]

Unfortunately, it isn't. Where else could it be referenced?

Do you have any code on the report with the deleted field in.
Are you running the report based on a query. Check to ensure you don't have any columns like
Expr1: Prog No


For the parameter value box to appear the deleted field must be referenced either in a query or there is a field on the report that is requesting the data from the recordsource.

Go into design view on the report to check the fields, just to make sure incase you have a field that is not visible when the report is run.

By the way is the report based on a query or a table.

Andy

 

[Pat Hartman]

Don't forget to look at the sorting and grouping properties.

 

[dataheadache]

By the way is the report based on a query or a table.

The report is based on a query - I've run the query on it own, and it does not ask for the Prog No. there - but does ask for it when the report is generated. Does this mean that the fault lies somewhere in the Report design, and if there is a hidden expression/field/text box etc. somewhere on the report - how do you make it visable to remove it?

 

[spacepro]

The report is based on a query - I've run the query on it own, and it does not ask for the Prog No. there - but does ask for it when the report is generated. Does this mean that the fault lies somewhere in the Report design, and if there is a hidden expression/field/text box etc. somewhere on the report - how do you make it visable to remove it?

Just to clarify, when you view your report in design mode, all of the objects on the report will be shown, whether there properties are visible or not.

Have you checked the suggestion by Pat?

The parameter could be a number of things:

• Deleted Field in Query
• Deleted Field is in the Sorting/Grouping Options of the Report
• The Deleted Field is still present on the Report
• The Report has VBA code that runs with the deleted field referenced.

I would suggest if you cannot find the field that is calling the parameter, for you to do two things.

1) Post a sample db with the Table/Query/Report in.

Or

2) Create a new report based on the query.



Andy

 

[dataheadache]

Don't forget to look at the sorting and grouping properties.

Silly me! It was there all along, wasn't it? I just kept looking past it.

Thanks to everybody for their help and suggestions as to what it could have been!