Skip to content

Latest commit

 

History

History
30 lines (22 loc) · 1.8 KB

chapter-7-handling-ado-events.md

File metadata and controls

30 lines (22 loc) · 1.8 KB
title TOCTitle ms:assetid ms:mtpsurl ms:contentKeyID ms.date mtps_version ms.localizationpriority
Chapter 7: Handling ADO events
Chapter 7: Handling ADO events
22924fe2-d00d-8a0c-52f5-2dc6039537ff
48543709
09/18/2015
v=office.15
medium

Chapter 7: Handling ADO events

Applies to: Access 2013, Office 2013

The ADO event model supports certain synchronous and asynchronous ADO operations that issue events, or notifications, before the operation starts or after it completes. An event is actually a call to an event-handler routine that you define in your application.

If you provide handler functions or procedures for the group of events that occur before the operation starts, you can examine or modify the parameters that were passed to the operation. Because it has not been executed yet, you can either cancel the operation or allow it to complete.

The group of events that occur after an operation completes are especially important if you use ADO asynchronously. For example, an application that starts an asynchronous Recordset.Open operation is notified by an execution complete event when the operation concludes.

Using the ADO event model adds some overhead to your application but provides far more flexibility than other methods of dealing with asynchronous operations, such as monitoring the State property of an object with a loop.

This chapter covers the following topics: