Chapter7.OpenLink OLE-DB Provider
Abstract
The OpenLink ODBC Provider for OLEDB is delivered as an OLEDB - ODBC bridge. It utilizes ODBC data sources to connect to databases, much like the Microsoft ODBC Provider; so you will require a working ODBC installation first.
The OpenLink Provider also requires that the Microsoft Data Access Components have been installed. To gain any functionality with .Net you will require MDAC 2.7 RTM (2.70.7713.4) or later. This particular version of the MDAC is included with Visual Studio .Net and with the .Net Framework SDK. Alternatively it can be downloaded from www.microsoft.com/data. Releases prior to 2.70.7713.4, specifically MDAC 2.7 included in the .Net SDK Beta 2, will not allow non-Microsoft OLE DB providers to work with the .Net Data Provider for OLE DB.
Although not completely necessary if you are using a newer OpenLink installer, before installing this provider, any previous release of the driver should be deinstalled fully. If a full deinstall using Install Shield is not performed, the old driver should be unregistered using the regsvr32 utility as follows:
regsvr32 /u
oploleod.dllTable of Contents
- 7.1. Testing an OLEDB Connection
- 7.2. Call Tracing
- 7.3. Provider Specific Connection Information
- 7.4. Controlling ODBC Cursor Library Usage
- 7.5. Controlling the Default Bookmark Setting for Rowsets
- 7.6. Known Issues
-
- 7.6.1. General Issues
- 7.6.2. .Net
- 7.6.3. Visual Interdev 6
- 7.6.4. Visual Basic 6 and ADO
- 7.6.5. SQL Server Data Transformation Services
- 7.7. Objects and Interfaces Implemented by the OpenLink Provider
-
- 7.7.1. Invoking the OpenLink Provider
- 7.7.2. Connecting from ADO or .Net
- 7.7.3. Initialization Properties
- 7.7.4. Initializing and Uninitializing the Data Source Object
- 7.7.5. Creating a Session
- 7.7.6. Creating a Rowset
- 7.7.7. Exposing Metadata
- 7.7.8. Supported Conversions
- 7.7.9. Creating and Using Accessors
- 7.7.10. Rowset MetaData