This one has me very puzzled because sometimes it works and sometimes it doesn't. I have several similar reports with slightly different filtering all creating FORMAT EXL2K Excel files to be burst and emailed.
The first BY field is AGENCY_NUMBER. Here are the ON TABLE statements:

ON TABLE SET PAGE-NUM NOLEAD
ON TABLE SET ASNAMES ON
ON TABLE SET HTMLCSS ON
ON TABLE SET XLSXPAGESETS ON
ON AGENCY_NUMBER HEADING
"Agency "Renewal Dates &RENEWAL_BEG - &RENEWAL_END"
" * Confidential - Internal information only"
ON AGENCY_NUMBER SUBFOOT
"**5 Year Claim Count is based on Notified Date of Loss"
ON TABLE SET ORIENTATION LANDSCAPE
ON TABLE PCHOLD FORMAT EXL2K
ON TABLE NOTOTAL
ON TABLE SET CACHELINES 100
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE SET SQUEEZE ON
ON TABLE SET HTMLCSS ON
ON TABLE SET GRWIDTH 1
ON TABLE SET HTMLENCODE ON
ON TABLE SET EMPTYREPORT ON
ON TABLE SET BYDISPLAY ON
ON TABLE SET STYLE *
-* INCLUDE = endeflt, $
INCLUDE=IBFS:/FILE/IBI_HTML_DIR/javaassist/intl/EN/ENIADefault_combine.sty,$
TYPE=REPORT, PAGESIZE=LEGAL, LINES-PER-PAGE=99, $

When the reports ran today, one of them broke the report into separate files based on the AGENCY_NUMBER field, but the others didn't; a single file with the data all on one tab with one heading but subfooters for each AGENCY_NUMBER value. The ON TABLE statements are the same for all the reports. Any ideas why it doesn't always work?

Thanks,
Deb

This message has been edited. Last edited by: DWaybright,

quote:

I have several similar reports with slightly different filtering.......The first BY field is AGENCY_NUMBER.

They all have AGENCY_NUMBER as the primary BY field?

quote:

....sometimes it works and sometimes it doesn't..... When the reports ran today, one of them broke the report into separate files based on the AGENCY_NUMBER field, but the others didn't;

The the report that did not burst properly, that report has run properly in the past?

And the reports that ran properly today, have not run properly in the past?

Don, That sounds like a DATA ISSUE...

The reports do all have AGENCY_NUMBER as the primary BY field. The ones that I ran before did work at least once. A couple of them are new, but I used all the same settings.

Can you send a copy of all the code for one report? Have you tried using EXL07 instead?

How many burst values do you have?

There is (was?) a limit on number of characters (in total) within the SUBHEAD/SUBFOOT of 32K(?), SO calculate the number of chars that all the SUBFOOTs produce and see if the total exceeds 32K on those reports that fail.

To me, unless you have an enormous number of burst values, the SUBFOOT doesn't look large enough to exceed 32K chars but it would be worth checking.

Might also be worth raising a case with Tech Support.

T

I ran some more tests and it seems to have to do with publishing the report and the schedule. I have all of them published now and will watch closely the next scheduled run. I will post the results.

Thanks all!

My reports burst as expected this time!
Making sure the schedule and the report are both published helped, but I also discovered (to my chagrin) that the burst option wasn't checked on some of these.
I am so grateful for your patience with us newbie goofs.

Thanks,
Deb