Ready for a quick Microsoft Access report quiz? This one covers a deceptively important idea: what actually controls how many times a report's Detail section prints. If you have ever built mailing labels, invoices, packing slips, or any report that mysteriously prints too many or too few rows, this is the stuff you need to know.
Grab a piece of paper, keep score if you like, and do not peek at the answers too quickly. There are five questions, all focused on Access reports, record sources, form references, and printing a full sheet of labels.
Question 1: What primarily determines how many times a report's Detail section prints?
A. The number of text boxes in the Detail section
B. The number of records returned by the report's Record Source
C. The number of pages selected in Print Preview
D. The number of controls on the form that opened it
Answer: B. The number of records returned by the report's Record Source.
In a normal Access report, each record returned by the report's Record Source gets one pass through the Detail section. If the report's query returns 13 records, the Detail section prints 13 times. If it returns 30 records, you get 30 detail positions. The number of text boxes and labels you put in the Detail section has nothing to do with the number of records Access processes.
This is the key idea behind many label-report tricks. Need 30 labels on a sheet? Give the report 30 records to process. Access does not care whether those records contain useful business data or are simply there to make the Detail section repeat.
Question 2: A report control uses an expression that refers to a control on an open form. What must be true when the report runs?
A. The form must remain open so Access can evaluate the reference
B. The form must be saved as a report first
C. The report and form must use the same Record Source
D. The referenced form control must be unbound
Answer: A. The form must remain open so Access can evaluate the reference.
If a report control contains an expression that reaches out to a form, Access has to be able to find that form at the moment the report is generated. A reference such as =Forms!CustomerF!FirstName reads the value from an open form named CustomerF.
If CustomerF is closed, Access cannot resolve that reference. You will generally get an error or an ugly little #Name? instead of the value you expected. The usual solution is to open the report from the form and leave the form open while the report is previewed or printed.
Question 3: Why might a label report use a small table containing exactly 30 otherwise meaningless records?
A. To permanently store each customer's mailing address
B. To make Access automatically create 30 new customers
C. To supply 30 Detail-section records for one full sheet
D. To force the report to use landscape orientation
Answer: C. To supply 30 Detail-section records for one full sheet.
This is a classic Access technique. You create a little helper table, sometimes called a numbers table, with 30 records. Those records can be nothing more than ID values from 1 through 30. The report uses that table as its Record Source, and Access prints the Detail section once for each record.
The labels themselves can contain calculated controls that read values from the currently open customer form. Since the report has 30 source records, Access produces 30 label positions, each showing the same customer's information. The table is not storing customer data. It is just giving Access a reason to repeat the Detail section 30 times. Think of it as a row generator. Not glamorous, but it gets the job done.
Question 4: Which Control Source expression correctly displays the FirstName control from an open form named CustomerF in a report text box?
A. [CustomerF].[FirstName]
B. =[CustomerF]![FirstName]
C. =Forms!CustomerF!FirstName
D. =Reports!CustomerF!FirstName
Answer: C. =Forms!CustomerF!FirstName
The Forms collection tells Access that you want to retrieve something from an open form. The first exclamation point identifies the form, and the second identifies the control on that form. The equals sign is important too, because it tells Access this is an expression to evaluate, not literal text to print.
You will use expressions like this when the report's Record Source is not the customer table itself. For example, your label report might use the 30-record helper table as its source, while each label reaches over to the open customer form to display the customer's name and address.
Question 5: A full-sheet label report repeats values from the current customer form 30 times. Why is it a poor choice when three labels need different text?
A. Reports cannot contain calculated controls
B. Changing the form value changes every repeated label that reads it
C. Access reports can print only one copy of each record
D. A report cannot use a table with 30 records
Answer: B. Changing the form value changes every repeated label that reads it.
If all 30 labels use expressions that point to the same form controls, they all evaluate the same values. Change the customer's FirstName on the form, and every label using that expression changes right along with it. That is perfect when you want a full sheet of identical labels. It is not so great when label 1 needs one message, label 2 needs another, and label 3 needs something completely different.
For individually editable labels, you need separate stored records for the individual labels, or some other process that creates separate data for each one. A report can certainly display calculated controls, and it can absolutely use a 30-record helper table. The problem is simply that all the repeated labels are reading the same source values.
So, how did you do? The big takeaway is that a report's Detail section is driven by its Record Source. Once you understand that, tricks like full-sheet label printing make a lot more sense, and Access stops looking quite so much like it is operating a wormhole behind your back.
If you want to see these report and label concepts in action, watch the embedded video. These topics are also covered in more depth in Microsoft Access Advanced Level 4.
Live long and prosper,
RR



