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.
TABLE FILE CAR
SUM
SALES
BY LOWEST COUNTRY
HEADING
"Report"
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE NOTOTAL
ON TABLE PCHOLD FORMAT HTML
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
TYPE=REPORT,
BORDER-TOP=LIGHT,
BORDER-BOTTOM=LIGHT,
BORDER-LEFT=LIGHT,
BORDER-RIGHT=LIGHT,
$
ENDSTYLE
END
In the output there is a blank line between the HEADING and the report. This is caused by WebFOCUS inserting
<TD COLSPAN=2 class='x3'>&.nbsp;</TD>
after the heading in order to close the border around the HEADING. Does anyone know a "simple" way to get rid of the blank line?
Ah well... I searched the Forum after I posted and saw the many requests... and still no solution...This message has been edited. Last edited by: <Emily McAllister>,
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006
Sadly that's still the case. And I doubt they'll ever fix it as it may have an impact on many existing reports that have been developed expecting that line there.
It would be interesting to have something like:
SET BLANKAFTERHEADINGONBORDER = { OLD | NEW }
Where: OLD -> Annoying blank line
NEW -> No blank line. Consistent behaviour (border or no border)
The setting name should be shorter obviously, I'm just trying to make a point here
@njsden Very true, it would leave other formats with the spacing issue and your idea of SET BLANKAFTERHEADINGONBORDER = { OLD | NEW } is the best one. I am wondering if the gap is for a subheading?
Developer Studio 7.7.02 Windows XP Pro SP3 and Windows 7 64bit all output
After some research. Using the same code in my first post, if we look at the generated HTML, this is what comes out. I changed all hard spaces to &.nbsp to see them. The offending blank is marked with ==>>:
You will notice that if one takes out the offending line, then the output is just as we would like it. So? Where is the problem? Can't the SET as proposed by njsden be added?
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006