clevelandjwb
Programmer
I am using MS Sql Server 7.0 and Crystal Reports 8.5.
I put this in the data access area because the problem has its root in data access even though the error message does not necessarily point to a data access problem.
I developed a rather complex query which involves the use of temporary tables before creating the final output table. To make testing of the both the query and report easier, I developed the query in Query Analyzer and simply created an output table. This same stored procedure is also going to have a life providing data to a WEB server so it was necessary at some point to make it a stored procedure.
I wrote and tested the report using the table created in Query Analyzer. Now I am attempting modify the report to used the stored procedure rather than the table that used to be created.
I went through "Set Location" for the database both in the report and a sub report. I fixed the linkages between the report and the sub report to use the new name. Everything looks right. The stored procedure seems to return the right data which I can see on the outline tree to the left of the report.
Before any real formatting of the report is complete I get the message: Group #1 ? - A <new line>
This group section can not printed because its condition field is non-existant or invalid. Format the section to choose another condition field <end of message>
Group #1 pulls together various reports that are going to the same person. It does not print either a header or a footer. It does not seem to have any selection formulae. Both the header and footer have "Free Form", "Hide" and "Keep Together" checked. All of the "X-2 pencil"'s are blue.
I would imagine that somehow I am still trying to reference the original data rather than the data coming back from the stored procedure.
Any help would be appreciated.
This gets worse. I did a little more testing as I proofread my post and have found that the problem might be data dependent although I can not determine what the data problem might be. In order to section a very long report into several shorter sections for printing, one pair of paramenters gives the starting letter and ending letter to select on the first character on the recipient's last name. When I run this report "a to a" I get the error message. When I run it "b to b" I get the error message. Just for fun I tried "c to c" as well as "d to d" and both of those produce a proper report ( e and f fail and g works).
John
I put this in the data access area because the problem has its root in data access even though the error message does not necessarily point to a data access problem.
I developed a rather complex query which involves the use of temporary tables before creating the final output table. To make testing of the both the query and report easier, I developed the query in Query Analyzer and simply created an output table. This same stored procedure is also going to have a life providing data to a WEB server so it was necessary at some point to make it a stored procedure.
I wrote and tested the report using the table created in Query Analyzer. Now I am attempting modify the report to used the stored procedure rather than the table that used to be created.
I went through "Set Location" for the database both in the report and a sub report. I fixed the linkages between the report and the sub report to use the new name. Everything looks right. The stored procedure seems to return the right data which I can see on the outline tree to the left of the report.
Before any real formatting of the report is complete I get the message: Group #1 ? - A <new line>
This group section can not printed because its condition field is non-existant or invalid. Format the section to choose another condition field <end of message>
Group #1 pulls together various reports that are going to the same person. It does not print either a header or a footer. It does not seem to have any selection formulae. Both the header and footer have "Free Form", "Hide" and "Keep Together" checked. All of the "X-2 pencil"'s are blue.
I would imagine that somehow I am still trying to reference the original data rather than the data coming back from the stored procedure.
Any help would be appreciated.
This gets worse. I did a little more testing as I proofread my post and have found that the problem might be data dependent although I can not determine what the data problem might be. In order to section a very long report into several shorter sections for printing, one pair of paramenters gives the starting letter and ending letter to select on the first character on the recipient's last name. When I run this report "a to a" I get the error message. When I run it "b to b" I get the error message. Just for fun I tried "c to c" as well as "d to d" and both of those produce a proper report ( e and f fail and g works).
John