As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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, MikeThis 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?
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
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.
_____________________ WF: 8.0.0.9 > going 8.2.0.5
Posts: 668 | Location: Veghel, The Netherlands | Registered: February 16, 2010
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.
WebFOCUS 7.7.05 (Someday 8) Windows 7, All Outputs In Focus since 1983.