I was just wondering if anybody else has encountered this issue. We have a PDF report that is doing a Page-Break with NOSPLIT to keep items grouped together when possible. This report has been used for several years now. In the WebFOCUS 7.7 environment, the report produces 193 PDF pages. In the WeboFOCUS 8.1 environment, the report produces 271 PDF pages. More of the pages have a lot more white-space left on them after converting to WebFOCUS 8. And items that were printed on a separate page could have easily fit on the previous page. Is there anyway to control the Page-Break behavior and make this report render like it did with WebFOCUS 7?

Thanks,
Mike

This message has been edited. Last edited by: <Emily McAllister>,

Are you using your own Stylesheet or the default one? I'm wondering if you run the report without the Stylesheet, will it reduce the number of pages it generates?

On a side topic, I'm still a fan of PRINTPLUS=ON when generating a PDF. It cuts down on white space.

I agree Kevin W, I always try to have PRINTPLUS combined with FILECOMPRESS when generating PDF, which cuts down on file size.

Did you try to set the number of lines to something very high? LINES = 9999

Worth trying perhaps.

have you tried using the new

DROPBLNKLINE settings?

From the "help" :
_______________________________________
DROPBLNKLINE


The syntax is:

SET DROPBLNKLINE = {OFF|ON|BODY|HEADING|ALL}
where:

OFF
Inserts system-generated blank lines as well as empty data lines. OFF is the default value.

ON|BODY
Removes system-generated blank lines within the body of the report, for example, before and after subheads. In addition, certain data lines that may be blank and appear as blank lines on the report output will be removed from the output. BODY is a synonym for ON.

HEADING
Removes the blank lines between headings and titles and between the report body and the footing. Works in positioned formats (PDF, PS, DHTML, PPT) when a request has a border or backcolor StyleSheet attribute anywhere in the report.

ALL
Provides both the ON and HEADING behaviors.

Thanks SWES, I will have to try FILECOMPRESS. Most of our PDFs, being for human consumption, are not that huge. However, SharePoint server space is at a premium so this technique may help.