|
Tag, Syntax and Example
|
Tag Description
|
Properties Description
|
rptReportHeader
{rptReportHeader [height=
<number of points>
] [force-new-page=
<"none","before-section","after-section" or "before-and-after-section">
]}
report header
{/rptReportHeader}
{rptReporHeader height=25} This is a report header {/rptReporHeader}
|
report header
|
height: Height of the section [default value is 0] (This property is usable only if you want to create a report split to pages for printing.)
force-new-page: Forcing the new page [default value is "none"] (This property is usable only if you want to create a report split to pages for printing.)
|
rptReportFooter
{rptReportFooter [height=
<number of points>
] [force-new-page=
<"none","before-section","after-section" or "before-and-after-section">
]}
report footer
{/rptReportFooter}
{rptReportFooter height=25} This is a report footer {/rptReportFooter}
|
report footer
|
|
rptPageHeader This tag is implemented only in AceHTMLReports Plus version
{rptPageHeader [page-height=
<number of points>
] [height=
<number of points>
] [force-new-page=
<"none","before-section","after-section" or "before-and-after-section">
]}
page header
{/rptPageHeader}
{rptPageHeader page-height=900 height=25} This is a page header {/rptPageHeader}
|
page header
|
page-height: Height of the page [default value is 756] (This property is usable only if you want to create a report split to pages for printing.)
|
rptPageFooter This tag is implemented only in AceHTMLReports Plus version
{rptPageFooter [height=
<number of points>
] [force-new-page=
<"none","before-section","after-section" or "before-and-after-section">
]}
page footer
{/rptPageFooter}
{rptPageFooter} This is a page footer {/rptPageFooter}
|
page footer
|
|
rptBody
{rptBody [order-by=
<order by clause>
] [height=
<number of points>
] [force-new-page=
<"none","before-section","after-section" or "before-and-after-section">
]}
report body
{/rptBody}
{rptBody order-by="ProductName DESC" height=35} This is a report body {/rptBody}
|
report body
|
order-by: Order by clause is the same as in SQL command [default value is ""];
|
rptGroupHeader This tag is implemented only in AceHTMLReports Plus version
{rptGroupHeader field=
<field name>
[sort-order=
<"ascending" or "descending">
] [group-on=
<"each-value", "prefix-characters", "year", "qtr", "month", "week", "day", "hour" or "minute">
] [group-interval=
<number of characters>
] [height=
<number of points>
] [force-new-page=
<"none","before-section","after-section" or "before-and-after-section">
]}
group header
{/rptGroupHeader}
{rptGroupHeader field="ProductName" group-on="prefix-characters" group-interval=1 height=35 force-new-page="after-section"} This is a group header {/rptGroupHeader}
|
group header
|
field: Field name used for grouping
sort-order: Ordering of the records [default value is "ascending"]
group-on: Specifies how you want the values grouped [default value is "each-value"]. The value depends on the field data type. For numeric fields is usable only "each-value". For text fields is usable "each-value" or "prefix-characters". Left values are usable for date fields.
group-interval: number of characters used for grouping if a group-on property is set to "prefix-characters" [default value is 0]
|
rptGroupFooter This tag is implemented only in AceHTMLReports Plus version
{rptGroupFooter [height=
<number of points>
] [force-new-page=
<"none","before-section","after-section" or "before-and-after-section">
]}
group footer
{/rptGroupFooter}
{rptGroupFooter} This is a group footer {/rptGroupFooter}
|
group footer
|
|
rptField
{rptField value=
<field name or expression>
[running-sum=
<"no", "over-group" or "over-all">
]}
{rptField value="ProductName"}
{rptField value="[ProductName]"}
{rptField value="Quantity" running-sum="over-group"}
{rptField value="=[Sum(Units)]"}
{rptField value="=iif([Sum(UnitsInStock)]<4000,'Less','More')"}
|
field
|
value: any expression contains field name, report functions, report variables or MS Access function. Using is similar to MS Access standard report with some differences.
First difference is using report function or report variables which must be quoted with [] brakets as in examples.
If you use MS Access function the delimiter is not ';' but it is standard ','.
Text used in expression is quoted by apostrophes not by string quotes.
running-sum: Running sum of field value [default value is "no"]
|
rptIf and rptElse This tag is implemented only in AceHTMLReports Plus version
{rptIf condition=
<expression>
]}
true part
[{rptElse}
false part ]
{/rptIf}
{rptIf condition="([body-record] mod 2)=0"} #FAFAFA {rptElse} #E8FFE8 {/rptIf}
|
conditioned printing
|
condition: any expression contains field name, report functions, report variables or MS Access function. Syntax is the same as in value property of the rptField tag.
|
|
Functions and Variables, Syntax and Example
|
Description
|
sum
[sum(
<field name>
)]
[sum(Quantity)]
|
sum of values
|
min
[min(
<field name>
)]
[min(Quantity)]
|
minimum of values
|
max
[max(
<field name>
)]
[max(Quantity)]
|
maximum of values
|
count
[count]
|
number of records in group
|
record
[record]
|
current record number
|
records
[records]
|
number of records
|
body-record This variable is implemented only in AceHTMLReports Plus version
[body-record]
|
current record number in group
|
page This variable is implemented only in AceHTMLReports Plus version
[page]
|
current page number
|
pages This variable is implemented only in AceHTMLReports Plus version
[pages]
|
number of pages
|
rest-of-page This variable is implemented only in AceHTMLReports Plus version
[rest-of-page]
|
rest of points to the end of the page when the page break is inserted
|
current-section This variable is implemented only in AceHTMLReports Plus version
[current-section]
|
name of the current section
|
