ADO Dynamic Property Index

Data providers, service providers, and service components can add dynamic properties to the Properties collections of the unopened Connection and Recordset objects. A given provider may also insert additional properties when these objects are opened. Some of these properties are listed in the ADO Dynamic Properties section. More are listed under the specific providers in the Appendix A: Providers section.

The table below is a cross-index of the ADO and OLE DB names for each standard OLE DB provider dynamic property. Your providers may add more properties than listed here. For the specific information about provider-specific dynamic properties, see your provider documentation.

The OLE DB Programmer's Reference refers to an ADO property name by the term, "Description." You can find more information about these standard properties in the OLE DB Programmer's Reference. Search for the OLE DB property name in the Index or see the following topics:

• Appendix C: OLE DB Properties
• Supported Properties of the Cursor Service
• Supported Properties of the Persistence Provider
• Supported OLE DB Properties of the Remoting Provider

Remarks

Note numbers used in the cross-index:

(1) This property is a Boolean flag indicating whether the named interface should be used. The equivalent OLE DB property name is listed if it exists.

(2) The "Bookmarkable" ADO property is generated internally for backwards compatibility, and is mapped to the OLE DB property, DBPROP_IROWSETLOCATE. This is the same property that corresponds to the ADO property, IRowsetLocate.

(3) The ADO property name, "Hidden Columns", is named differently than the OLE DB property name Description, "Hidden Columns Count."

(4) For hierarchical recordsets, the "Maximum Rows" ADO property gets applied across all children. Depending on the order in which the rows are returned, you might have all, some or no children for each parent or orphaned children in the result set. Therefore, when reshaping hierarchical recordsets, the identifier for every child should be unique. In general, the Microsoft Data Shaping Service for OLE DB (MSDATASHAPE) provider does not allow for distinction between properties that can be inherited from the parent and those that cannot be inherited.

(5) Does not apply.

Connection Dynamic Properties

Recordset Dynamic Properties

Note that the Dynamic Properties of the Recordset object go out of scope (become unavailable) when the Recordset is closed.