quote:

The Product Division has reviewed as follows: The requested behavior would require a major reworking of core border code therefore we can not accept this as a new feature request.

quote:

When HTMLCSS is set to ON, a line is generated when there is no HEADING because of a WHEN statement. Also, why is an extra row of blank data generated at the bottom of the report when BORDER is set to 1?

TABLE FILE CAR
SUM
SALES
COMPUTE DOWK/A3 = DOWK(&YYMD,'A3');
BY COUNTRY

HEADING
"REPORT HEADING"
WHEN DOWK NE 'WED'

ON TABLE SET PAGE NOLEAD
ON TABLE SET HTMLCSS ON

ON TABLE SET STYLE *
TYPE=REPORT, SQUEEZE=ON, FONT='ARIAL', SIZE=9, BORDER=1, BORDER-COLOR=SILVER, $
ENDSTYLE
END

TABLE FILE CAR
SUM
SALES
BY COUNTRY
HEADING
"REPORT HEADING"
WHEN COUNTRY EQ 'INDIA'
ON TABLE SET PAGE NOLEAD
ON TABLE SET HTMLCSS ON

ON TABLE SET STYLE *
TYPE=REPORT, SQUEEZE=ON, FONT='ARIAL', SIZE=9, $
TYPE=DATA, BORDER=1, BORDER-COLOR=SILVER, $
TYPE=TITLE, STYLE=BOLD, BORDER=1, BORDER-COLOR=SILVER, $
TYPE=HEADING, BORDER=1, BORDER-COLOR=SILVER,
-****
-***** below is the line to make the BORDER styling conditional
-*****
WHEN=COUNTRY EQ  'INDIA'  ,
$
ENDSTYLE
END

quote:

I have been informed that this is not a bug but is expected behavior.
There is no way to remove these lines. Per Product Management, Bordered HTML
reports have always presented with these blank lines between the heading /
footing and body nodes in border mode.

Any mention of border styling in the Stylesheet will cause this behavior.
Additionally HTMLCSS is required for borders to present so the behavior of any
borders or associated blank lines will correspond to the presence of this
syntax.

When a HEADING is conditionally displayed or not displayed the blank line
that would normally appear between the HEADING and the body of the report
are not conditionally removed.

I have requested that this be documented but can also submit a NFR
on your behalf to have the blank line conditionally display.

Please let me know if you would like me to submit the new feature request
and if there are any further questions on the above information.

I will place the case into customer testing and await your update.

For the second issue, this is a long standing Core FOCUS issue. The
long standing solution is to use a SUBFOOT or SUBHEAD, if you prefer, with
subtotals. This should not occur with FORMAT HTML but would occur for
FORMAT PDF.

quote:

Thanks for the update. Just because it is "expected behavior" doesn't mean
it's not a bug.
Yes, please request a NFR for this. This issue had been mentioned many
times on FocalPoint and there are quite a few people that would like this
fixed.
Another example of "expected behavior" that is extremely annoying is the
TOTAL line split into two because there's a BY XYZ NOPRINT - now I'm sure
that there is no WebFOCUS developer that wants that to happen and yet it's
been there since the beginning of FOCUS.

For the second problem - yes, it shouldn't happen, but it does, and that is
where the frustration is.

quote:

Thank you for bringing this problem to our attention. We have reviewed it
with our engineering staff and it has been determined that it will not be
implemented in the WebFOCUS product. Therefore, we will close the case.
If this decision substantially impacts your business, please discuss with
your local account support team.