Weird error message

  • Thread starter Thread starter Jonathan Blitz
  • Start date Start date
J

Jonathan Blitz

I have started to get a weird message when running a report.

I get the message:

Column (ReportedDate) was used in a CALC expression but is not defined in
the rowset.

What does it mean. I haven't changed anything.

The column ReportedDate is in the data and is also one of grouping levels.

This is the second time it has happened to me with the same report. I really
can't face rebuilding it again.

HELP!

--
Jonathan Blitz
AnyKey Limited
Israel

"When things seem bad
Don't worry and shout
Just count up the times
Things have worked themselves out."
 
Hi Jonathan,

Based on my experience, the error is related to InputParameter property in
adp, we should use the correct syntax in reports. To resolve the issue,
check the syntax of the InputParameter property.

Forms!formname!controlname will work for one parameter but not in
conjunction with a main report/sub report

The correct syntax should be

@ParamName=Forms!formname!controlname

Please let me know if the above information helps. If you have any
questions, please feel free to reply to the threads.



Sincerely,

Alick Ye, MCSD
Product Support Services
Microsoft Corporation
Get Secure! - <www.microsoft.com/security>

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Jonathan Blitz" <[email protected]>
| Subject: Weird error message
|
| I have started to get a weird message when running a report.
|
| I get the message:
|
| Column (ReportedDate) was used in a CALC expression but is not defined in
| the rowset.
|
| What does it mean. I haven't changed anything.
|
| The column ReportedDate is in the data and is also one of grouping levels.
|
| This is the second time it has happened to me with the same report. I
really
| can't face rebuilding it again.
|
| HELP!
|
| --
| Jonathan Blitz
| AnyKey Limited
| Israel
|
| "When things seem bad
| Don't worry and shout
| Just count up the times
| Things have worked themselves out."
|
|
|
 
Try This?

I recieved the same error after altering column names, then trying to run the report again. I sucessfully renamed the control sources on the report, but couldn't find the source of the error, even after searching through all the related code and form properties.

I finally determined the cause was I had set up a sort using the old column name.

To fix this, I rclick on the form, chose "Sorting and Grouping", then using the down arrow changed the name of the colum to the updated column.
 
Back
Top