OLE DB Consumer Templates (C++)

The OLE DB Consumer Templates support the OLE DB version 2.6 specification. (The OLE DB Consumer Templates are tested against OLE DB 2.6 but don't support every interface in the specification.) The Consumer Templates minimize the amount of code you must write to implement an OLE DB consumer. The templates provide:

• Easy access to OLE DB features and easy integration with ATL and MFC.

• An easy binding model for database parameters and columns.

• Native C/C++ data types for OLE DB programming.

To use the OLE DB Templates, you should be familiar with C++ templates, COM, and the OLE DB interfaces. If you aren't familiar with OLE DB, see Microsoft OLE DB Driver for SQL Server.

The OLE DB Templates support the existing OLE DB object model rather than adding a new object model. The top-layer classes in the OLE DB Consumer Templates parallel the components defined in the OLE DB specification. The design of the OLE DB Consumer Templates includes advanced features such as multiple accessors on a rowset. The use of templates and multiple inheritance makes the library small and flexible.

How OLE DB Consumers Access Data

Consumers use several kinds of objects, which are described in the following topics:

• Data Sources and Sessions

• Accessors and Rowsets

• Commands and Tables

• User Records

Before the consumer does anything, you first select an OLE DB provider that is appropriate for the type of database you need to access (for example, SQL, Oracle, ODBC, and MSDS). To do this, you typically use an enumerator (see CEnumerator as mentioned in Data Sources and Sessions).

The data source object provides the connection information necessary to connect to the data source you selected. The data source object also contains authentication information (such as login names and passwords), which is used to give users permission to access the data source. The data source object makes a connection to the database and then creates one or more session objects. Each session object manages its own interactions with the database (that is, querying and retrieving data) and performs these transactions independently of other existing sessions.

The session creates the rowset and command objects. The command object allows users to interact with the database, for example, using SQL commands. The rowset object is a set of data through which you can navigate and in which you can update, delete, and insert rows.

An OLE DB consumer binds columns in the database tables with local variables; to do this, it uses an accessor, which contains a map of how data is stored within the consumer. The map consists of a set of bindings between table columns and local buffers (variables) in the consumer application.

One important concept when working with consumers is that you declare two classes in a consumer: the command (or table) class and the user record class. You access the rowset through the command (or table) class, which inherits from both an accessor class and a rowset class. The user record class contains the rowset binding map previously described.

For more information, see the following topics:

• Creating an OLE DB Consumer

• Common OLE DB Consumer Scenarios (Examples)

See also

OLE DB Programming
Data Access
OLE DB SDK Documentation
Microsoft OLE DB Driver for SQL Server