Present data

A one-off summary calculation (total, MAX, MIN, COUNT) goes in the report footer, shown once. Identification details that must show on every page go in the page footer. Swap them and both fail: a summary in the page footer wrongly repeats (and may recalculate) on every page; details in the report footer appear only once, on the last page.

A report wizard often inserts default text such as "Query 1" into the title area; this must be replaced with the intended title, not left alongside it. Titles also lose marks for data-entry or capitalisation errors in the text. Read the required title from the task and type it exactly -- correct wording and capitalisation -- removing any wizard placeholder first.

The report title is usually set in a larger font. If the title's text box is not resized for that font, the descenders -- the tails on g, y and p -- are cut off at the bottom, even though the rest looks correct. Fix by enlarging the text box so the whole character shows; do not shrink the font, which would fail the required size.

A column or field box left too narrow cuts off part of a value or a field-name label, so the data is not fully visible even though it is correct in the table. This fails the "display all data and labels in full" requirement regardless of the data being right. Widen the column or box until every value and heading shows completely.

The task specifies the orientation (portrait or landscape) and how many pages the report should fit. A report in the wrong orientation, or one that spills onto extra pages because columns are too wide, does not match the evidence the mark scheme expects. Set the orientation the task names and check the report fits the specified page count.

A newly added calculated field is often left in its default alignment instead of being right-aligned (and decimal-aligned) to match the numeric column beside it, so the value does not line up with the existing numbers. Numbers are right-aligned by convention; set the field to match its column, lining up the decimal points where decimal-place counts differ.

A calculated field derived from an already-formatted field -- e.g. a discounted price from a Price field shown to 2 decimal places with a currency symbol -- is often left unformatted, shown as a raw number. Apply the same currency symbol and decimal places as its source field so related money fields match. Formatting changes only the display, not the stored value.