Editor: set of C++ classes wrapping the ODBC and OLE DB database APIs.
Database classes designed to seamlessly MOVE Between ODBC and the OLE DB interface without code changes. Designed with a generic database interface and a class Factory pattern to remove traces of any technology specific class implementation.
The classes expose storage information in the traditional Recordset and Command object types.
The ODBC classes are being tested with various database vendors, while the OLE DB classes are still in development. The OLE DB wrappers require the ATL atlbase.h file to be included.
You are probably asking why you would not just use the ATL OLE DB Client (Consumer) classes? After all, you can access ODBC through the "OLE DB Provider for ODBC"? I don't really have a good answer to that one, except perhaps for the need for good performance with both ODBC and OLE DB in the same app.
