Only applicable when the field is used as a break. The default is 'No'. Answer 'Yes' to modify what happens when the field breaks. The effect of this option is to prevent fields in this break and below from being printed in sub-total lines for breaks above.
This is best explained by way of example. In the SALESORD database, material orders are stored in the ORDER_LINE table. Now, suppose a daily sales report is required where the total number and value of each material sold is displayed together with a grand total of the materials' value. You set up the report as follows:
Field Sort List? List on break? Break? Total?
MATERIAL_CODE 1 No Yes Yes No
QUANTITY No Yes No Yes
LINE_VALUE No Yes No Yes
The report output takes this form:
Material Quantity Line
Code Value
19949819 676 845.00
19949826 199 509.44
...
69840 30841.35
Note
The last line is the grand total line. Notice that it contains a grand total for the quantity field which is not a useful value to display.
To prevent the total number of materials sold from being displayed you can use the local break facility and set up a slightly more complicated report, as in:
Field Sort List? List on break? Break? Total? Local Brk?
DUMMY='X' No No Yes No No
HEADING='Total' No Yes No No
LINE_VALUE No Yes No Yes
MATERIAL_CODE 1 No Yes Yes No Yes
QUANTITY No Yes No Yes
LINE_VALUE No Yes No Yes
This report prints the totals needed for each material code. A break is generated on the DUMMY field at the end of the report, simulating the grand totals. The total materials' value is printed in this break. Without the local break field, totals for the QUANTITY and second LINE_VALUE would be printed as well.