Event properties are used in reports, much the same way that they are in forms. The difference is that there are no properties that the user can initiate. Everything is done by the developer. There are no buttons to click, no combo boxes to open, or no data validation to perform.
Figure 11-1 and the following table display the extent of the event properties, and what causes them to be executed for a report. Some of these properties will be demonstrated in the code samples later in the chapter
|Property||Triggers When. . .|
|On Open||The report is opened|
|On Close||The report is closed|
|On Activate||The report preview window is activated|
|On Deactivate||The report preview window is deactivated|
|On No Data||The recordsource of the report contains no records|
|On Page||After a page is formatted, but before it is printed|
|on Error||An error occurs during the execution of code|
When you are ready to begin associating VBA code to an event property, this is how you instruct Access to use your VBA code: You can start from either the Design View of the Report or from the VBA Editor window itself. Both methods are useful, and the times at which you utilize them will depend on your current location (Report or Editor) at the time that you need to start a new procedure.
From the Report Design window, click to highlight the desired ...