I am trying to generate a No Data message for a coordinated compound pdf report that bursts on the high-level sort field and is run in ReportCaster.

I have a section in the pdf reports that it branches to handle for No Data, but it does not work with the coordinated compound pdf reports. I have tried to get it to work for 1 bursted value for the coordinated compound pdf report and it does not work. I get the "no report to distribute" error message in the ReportCaster log. I guess there is an issue with no data error handling like this working in conjuction with coordinated compound reports.

I wonder if setting EMPTYREPORT some way will work with coordinated compound pdf reports. Has anyone done anything with setting No Data for coordinated compound reports or have any suggestions?

Maybe...

If you can already detect that you have no data and branch to a different path when such a thing, you should built a PDF compound "No data" report and distribute this one instead.
That way RC will have the same report format to distribute no matter what

MartyY - Thanks...I can possibly look into that. However, what I just discovered is that my bar chart procedures which is contained as one of the procedures in the compound pdf layout is producing a crashed agent whenever there is a no data output scenario. So when I execute the compound pdf layout procedure within RC for a no data situation, it gives me the "no report to distribute" error message.

So I need to determine why that procedure is producing a crashed agent in a no data scenario.