not supported

[steverdan]

I am working on a report with multiple sub-reports. Over the weekend my sub-reports started failing, most due to connection issues with a local DB vs our box software sequel server db. However, I have got one sub report that simply gives the error of "not supported" but I am unsure what is not supported? There are thousands of possibilities if this is a line item issue. So how do I find out what is not supported?

[JWiseman]

p.s. In addition to the above, in your 1st newly saved report, go to the subreport Record Selection formula and comment it out. Put in a generic selection formula to limit the number of records...{one of your number fields} = 0.

[JWiseman]

OK now we're getting somewhere...it could still be related to the DB issues that you mentioned, but try to figure out if it's a particular object on the subreport that is responsible. (Reports still can error out with bad data and that changes over time.)

To test the report only theory, do a Save As 2 / two times for the main report. i.e. The report that contains the problem subreport.

With the first newly saved report, open up the problem subreport and then delete absolutely everything off this subreport report. Try running the main report in Crystal.

If it runs OK, then go to the second newly saved report without the deletions. Delete one section or group at a time and then keep rerunning. It's a bit of a pain, but as you said there could be a thousand possibilities. Date time fields, SQL Expressions, grouping on server, and linking enforced by report canvas objects all come to mind.

[steverdan]

This is not a new report. It ran fine last week. It doesn't give me the error when ran as stand alone, but does when it is attached to the full report. When not attached I get blank report, so obviously this is report based. The main report runs against this same database and no errors if I unhook this report. Nothing has changed on this report in years. I can run the qry through access and data is fine. so back to the original question, how do I find out what is not supported?

[JWiseman]

You don't need to recreate the subreport...it's a simple Save As new report; please see the aforementioned test procedure.

Once you've saved the report as a new test report you can provide parameter values to run the subreport that you believe should bring back data. You can also verify the data by going to the Database menu > Show SQL Query and run that against your DB.

[steverdan]

See what I said above. When I substitute data set I get back a blank report even though there should be data.

[steverdan]

sub report needs data from the main report to know what to look at. When I substitute data set I get back a blank report even though there should be data. This is a huge sub report so recreating will take several hours and I was trying to avoid that. Thanks for the help though.

[JWiseman]

hi Steve, you'd need to provide a bit more info on versions, DB & what's being consumed in the report, etc.

1. To start try doing a Save As with the Subreport and running this test report on its own.
2. Delete all of the objects off of the saved test report and rerun.
3. Create a new report based off of an identical connection and tables or procs etc. as the subreport.
4. If the error persists then try running an identical SQL query against your DB query tool.

[JWiseman]

I did see that; this is why you also need to run the SQL query generated by the subreport, after the provided parameter values, against your DB...i.e. this is the verification process to see if the issue is purely report based or DB based.

The SQL query run by the report is generated using the Record Selection Formula in conjunction with table linking.

If you run this query against your DB query tool and it does bring back records, then the next step is to go back to your report and check on the Section Expert's suppression formulae, Group Selection Formula.

If running the query against your DB query tool and this returns 0 / zero records, then you need to evaluate the Subreport's Record Selection formula (and how this works with the subreport link parameters) and also the table linking.