Generating Reports › Formatting Based on Column Value Control Break › Identifying Control Breaks on the Report › Annotated Control Break Footings

Annotated Control Break Footings

It is often helpful to document how many group details were printed in a control group. RDF automatically accumulates and prints that value as part of the footing if requested to do so on the Parameter fill‑in.

For example, if you request annotation on the previous control footing example and fifteen customer detail lines were printed for Texas, the footing prints as the following:

STATE TX
COUNT               15

You can obtain additional types of information based on the control group. This summary information is described in the Generating the Bottom Line section. Summary information, including COUNT, is most meaningful when the records are sorted according to the control break field. This means that the FOR construct must include an ORDERED BY clause to access the records in the required sequence.

Note: To combine these examples, assume the report contains the customer name, city, state, and outstanding amount owed. A control break is specified on CUSTOMER.STATE. A second level control break is specified on CUSTOMER.CITY. The FOR construct accesses the data ordered by state and then by city. Control break headings and footings are to be printed. Control break footings are to contain annotated totals. The value of CUSTOMER.STATE is not to print on the detail line as specified on the Detail fill‑in. The value of CUSTOMER.CITY prints only when the value changes. The Detail fill‑in is defined as shown in the following screen:

 =>
‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
 IDEAL   : RPT DETAIL DEFN.      RPT CUSTRPT  (001) TEST           SYS: DOC  DISP 

         Field Name, Literal,      Sort   Break  Function Column 
         Function, or               L A   L S I  T M M A  H W    
 Command Arithmetic Expression      V /   V K N  O A I V  D ID Tab Edit Pattern 
                                    L D   L P D  T X N G  G TH   
 ‑‑‑‑‑‑  ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑  ‑ ‑   ‑ ‑ ‑  ‑ ‑ ‑ ‑  ‑ ‑‑ ‑‑‑ ‑‑‑‑‑‑‑‑‑‑‑‑‑
 ======  =========== T O P =======  = =   = = =  = = = =  = == === =============
 000300  CUSTOMER.NAME              _ _   _ _ _  _ _ _ _  _ __ ___ _____________
 000400  CUSTOMER.CITY              _ _   2 2 G  _ _ _ _  _ __ ___ _____________
 000500  CUSTOMER.STATE             _ _   1 2 N  _ _ _ _  _ __ ___ _____________
 000600  CUSTOMER.OPEN$             _ _   _ _ _  _ _ _ _  _ __ ___ _____________
 ======  ========= B O T T O M ===  = =   = = =  = = = =  = == === =============

The output for Texas prints as the following:

 .
 .
 .
	** STATE TX
	**** CITY DALLAS
	GULF LAND USA             DALLAS             7,100.00
	TEXAS LIFE & CASUALTY                          543.21
	AFTON INDUSTRIES                             1,234.00
	     CITY DALLAS
	     COUNT          3 

	**** CITY FORT WORTH
	CHEMICAL MUTUAL           FORT WORTH           931.72
	PALMOLIVE INNS                                 758.93
	     CITY FORT WORTH
	     COUNT           2
	     STATE TX
	     COUNT           5
 .
 .
 .

Even though column headings were suppressed on the Parameter fill‑in, the control break headings and footings print for each level of control break, using the default column headings.