Crystal Reports: cannot determine the queries required to get data for this report
I recently encountered the following error in one of my crystal reports after updating the accounting system.
Group # 1 :? - A: This group section cannot be printed because its condition field does not exist or is invalid. Format the section to select a different condition field.
I checked every field in the database that is used to ensure it still exists for consistency and checked the formulas for this section. No cubes. So hopefully to fix the problem, I am deleting the section using the section expert. I am running the same database checks. Then he complains about the same error for group # 5. So I am deleting that too.
I now have a new and unusual error when I try to run Show Query.
error: "Unable to determine the queries required to get data for this report"
I tried to login / log out of the database and check the database. No complaints until I try to run, show the request. When I try to run the report, it also throws the same error.
any ideas? Am I approaching this the wrong way? this is done in crystal reports 10.
Note: this report is run with sql sa user to troubleshoot any permission issues.
a source to share
I understood that. I ended up rebuilding the entire report and re-inserting the same fields into the report along with rebuilding the groupings. As soon as I did this and compared the multiple references, it turns out that some of the table references were deleted for some reason.
a source to share
For me, this problem occurred when there were two possible starting points for the request. If you go to a database expert and check the referral direction. You may find that links don't all go from left to right (say). As a result, Crystal cannot decide which queries to start with.
a source to share
I ran into this error in a non-grouping related setup. My data model was like this:
A -> B -> D
A -> C -> D
s ->
being the links to the parts. So I was actually using object D as a part of two different wizards that apparently are not allowed in Crystal Reports.
So I adjusted the model as follows:
A -> B -> D
A -> C*
by including all D attributes in C * and denormalizing the data when fed into Crystal Reports. And that was exactly the moment when the runtime error started. However, in my report using A and C *, I did NOT replace the D attributes with the corresponding C *. So the query engine was trying to reach attributes in D coming from C * that didn't work.
Replacing the attributes in D with new ones in C * fixes the problem.
a source to share
