VB6 - Disconnected, Persistent, and Dynamic Recordsets

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.

See Also

• Initializing the Connection Object in Code
• Connection Object Events
• Initializing Command Objects in Code
• Recordsets
• Manipulating a Recordset's Data With Its Methods
• Referring to Recordset Field Contents
• Programmatically Reading a Record's Contents Into VB Controls
• Programmatically Writing VB Controls to a Record
• Updating a Record
• Canceling User Changes Before They Are Saved
• Adding a Record
• Deleting a Record
• Programmatically Navigating a Recordset
• Locating Records
• The Recordset's Bookmark Property
• Recordset Events
• Disconnected Recordsets
• Dynamic Recordsets
• Persistent Recordsets
• Using the ADO Errors collection