fix problem in report

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a report that I changed one of the grouping fields to a new field and
removed the original field from the query. My report still thinks that field
exists and won't run without asking for the field data. Is there a way in
access, like there is in foxpro to open the report in a table format so that
I can search for where the problem is and fix it?

If there isn't a way to open it as a table, is there another way to locate
the problem field so that is can be corrected?
 
It sound like the parameter within the query is still set to the value of
the deleted field.

Try opening the query in design view, and then select Parameter, Query.. and
if that parameter is still there then you'll need to remove it.

HTH
 
The field was not in the query. I solved the problem by creating a new
report in design view with the proper grouping and then copying all the
fields from the bad report to the new report. The new report works fine.
The problem is in the backend of the report. What would help is if there is
a way in access to view the actual code that creates the design of the
report. As I mentioned, FoxPro stores all that information in table format.
If this kind of issues occurs you open the table that is the report design
and search the fields for the problem. I was hoping there is a way in access
to do the same.
 
Back
Top