These variables are used to modify the default content of a HTTP header sent to the client. They can be very powerful tools in building complex web solutions.
WB_HTTPHeader
WB_AddCookie
WB_ContentType
WB_Redirect
read more
Showing posts with label header. Show all posts
Showing posts with label header. Show all posts
Tuesday, October 19, 2010
Tuesday, October 5, 2010
Header and Footer sections
Header and footer are subsections of detail section. When used they must be placed on the very beginning (header) and very end (footer) of the detail section. This means that nothing (HTML code, RTF tags, plain text, etc.) can not be placed between and and/or between and . This is an example of correctly placed header and footer (marked blue):
$wbsetv[countbooks|0]
This is the list of titles for year $wbf[year published]
$wbf[title] - $wbf[isbn]
$wbsetv[countbooks|$wbcalc[$wbgetv[countbooks]+1]]
Total books in $wbf[year published]:
$wbgetv[countbooks]
$wbsetv[countbooks|0]
Header and Footer sections will be processed and sent to the client before and after Detail section whenever any of referent fields change it's value (to learn more about referent fields please read the explanation for input variable WB_ChangeHFOn). Header and Footer sections will also be shown at the beginning of the Detail section for first record and at the end of the Detail section for last record on the report.
read more
$wbsetv[countbooks|0]
This is the list of titles for year $wbf[year published]
$wbf[title] - $wbf[isbn]
$wbsetv[countbooks|$wbcalc[$wbgetv[countbooks]+1]]
Total books in $wbf[year published]:
$wbgetv[countbooks]
$wbsetv[countbooks|0]
read more
Friday, August 13, 2010
5054 - WB_Order does not start with WB_ChangeHFOn
This error is generated when both variables exist and fields specified in WB_ChangeHFOn are not the same as starting fields in WB_Order.
read more
read more
Subscribe to:
Posts (Atom)