||Oracle Tips by Burleson
The display position indicates where the
pagination will be displayed in relation to the report region.
Number of Rows
Defines the maximum number of rows displayed in
the report at one time. If the Number of Rows attribute is used, this
attribute will be ignored.
Max Row Count
This is the maximum number of rows the HTML DB
engine will count if one of the pagination schemes that display X to Y
of Z is used. This helps prevent huge performance problems if the
query returns thousands of rows.
This will allow HTML DB to strip out any HTML tags
and will prevent conflicts. This option should almost always be set
to YES. The reason for this is that if data is selected from the
database and it contains HTML tags, it can cause conflicts with the
page being rendered.
These are the sorting icons displayed in the
column headings of the sorted row. They are different depending on
whether the row is sorted ascending or descending. Use the links
change the sorting icon. It is also possible to provide the
developers own images to display here.
These are messages displayed to the user in the
report region. The When more data found messageitem works together with the Max Row Count.
If more rows exist than were allowed by the setting in Max Row Count,
this message will be displayed at the end of the report.
This was detailed in the Adding the Spread Sheetlink section earlier in the chapter.
To keep the figures in the book small, the list
of columns has been narrowed and a WHERE clause added that reads:
(WHERE first_name like '%an%'). So, do not be alarmed if your
results look different.
The best way to
explain this is to create a report and put Break Formatting to work.
You already know how to create a new SQL Report using the wizard.
Navigate to the Easy HTML DB Book application and create a SQL report
with page id 1071 using the SQL statement from file ch7_1.sql. Name
the page Break Formatting for easy reference later.
After the report has been created, navigate to the
Report Attributes page. Figure 7.16 shows what the Break Formatting
region should look like before the Apply Changes, but here is an
explanation of what is done.
The first thing was to move the PAYMENT column into the
first column position. This is done by clicking on arrows shown in
Display this text when printing report sums: This is
the text that will be printed at the end of the report for the grand
total of the report. This is printed at the bottom of Figure 7.17.
Breaks: This has a couple of options such as First
Column, First and Second Columns, and First, Second and Third
Columns. Since the break group was to be on the payment, that column
was moved to the first position and selected the First Column option.
Display this text on report breaks using #SUM_COLUMN_HEADER#
substitutions: The column heading of the payment column is Pmt Type.
This is the heading that will be substituted for the #SUM_COLUMN_HEADER#
substitution string in each of the break groups. The text Total for:
has been added. To see how this is displayed in the report, refer to
Identify how you would like your breaks to be
displayed: The truth is there are some things that are just too
difficult to explain. They are much easier done than said! So, I
encourage you to change this setting to other options and see how it
For repeating heading breaks use this format: The #COLUMN_VALUE#
substitution string is taken directly from the value of the break
column. In Figure 7.17 it is being displayed with the values Cash,
Check, and -null- from records with no payment data. Some font tags
have also been added for formatting as well as the text “Payment
Type:”. This text is only displayed if the Repeat Headings on Break
option was used from above. That phenomenon will be observable if the
value is changed and the page rendered to see the difference.
For more details and scripts, see my new book "
Tuning: The Definitive Reference", over 900 pages
of BC's favorite tuning tips & scripts.
You can buy it direct from the publisher for 30%-off and get
instant access to the code depot.