Because ADO has a "flat" object model hierarchy, with few dependent
objects (that is, few objects that can only be accessed through other, parent
objects), ADO Recordsets present some new possibilities that were not available
with earlier Microsoft data object models, such as DAO.
In particular, a Recordset
does not always need to be connected to a Connection object. In fact, it is possible
to create a Recordset that never uses a Connection object or connects to data
outside your application.
At first glance, these possibilities may seem more like curiosities than like
practical features of the Recordset object, but let's look a bit more closely
at the different possibilities of unconnected Recordsets:
-
Disconnected Recordset objects. Enable you to reduce server overhead by processing
data offline.
-
Dynamic Recordset objects. Give you the full power of the ADO model to manipulate
data that's completely internal to your application.
-
Persistent Recordset objects. Free you from having to complete all actions
on a Recordset during a single session of the application.
