ADO Objects and Interfaces
The relationships between these objects are represented in the ADO Object Model.
Each object can be contained in its corresponding collection. For example, an Error object can be contained in an Errors collection. For more information, see ADO Collections or a specific collection topic.
|
Used to retrieve the underlying OLEDB Command from an ADOCommand object. |
|
|
Constructs an ADO Record object from an OLE DB Row object in a C/C++ application. |
|
|
Constructs an ADO Recordset object from an OLE DB Rowset object in a C/C++ application. |
|
|
Constructs an ADO Stream object from an OLE DB IStream object in a C/C++ application. |
|
|
Defines a specific command that you intend to execute against a data source. The Command object is not safe for scripting. |
|
|
Represents an open connection to a data source. The Connection object is safe for scripting. |
|
|
Gets the underlying OLEDB Data Source object for the SHAPE provider. |
|
|
Contains details about data access errors that pertain to a single operation involving the provider. The Error object is not safe for scripting. |
|
|
Represents a column of data with a common data type. |
|
|
Represents a parameter or argument associated with a Command object based on a parameterized query or stored procedure. The Parameter object is not safe for scripting. |
|
|
Represents a dynamic characteristic of an ADO object that is defined by the provider. |
|
|
Represents a row of a Recordset, or a directory or file in a file system. The Record object is safe for scripting. |
|
|
Represents the set of records from a base table or the results of an executed command. At any time, the Recordset object refers to only a single record within the set as the current record. The Recordset object is safe for scripting. |
|
|
Represents a binary stream of data. The Stream object is safe for scripting. |
