Differences between the Access ODBC Driver and the native OLE DB Provider for Microsoft Jet
Clients converting code from the Access ODBC Driver to the native OLE DB Provider for Microsoft Jet should be aware of the following issues:
The native Jet Provider has no notion of a catalog as defined in OLE DB. The DBPROP_DATASOURCE property defines the database to use, and the ODBC driver treats this database as the current catalog. The DBPROP_CURRENTCATALOG property does not provide additional information to users about the current data store. Also, the native Jet Provider does not support the ability to change the current data store. Clients wanting to change the data store should uninitialize the data source object, set the new data store name, and reinitialize the data source object.
The native Jet Provider does not parse the same SQL syntax as parsed by the Access ODBC Driver. Clients should use the DBPROP_SQLSUPPORT property and the IDBInfo interface to query clients for their SQL support capabilities.
Differences between versions 3.5 and 4.0 of the OLE DB Provider for Microsoft Jet
Important areas of functional differences between the 3.5 OLE DB Provider for Microsoft Jet and the 4.0 Provider include the following: