http://docs.openlinksw.com/mt/oledb.html OLE-DB Client Provider Multi-Tier User Guide 2008-04-09T14:37:12Z http://docs.openlinksw.com/mt/../images/mt/misc/logo.jpg http://docs.openlinksw.com/mt/oledbtest.htmlTesting an OLEDB Connection 2008-04-09T14:37:12Z Testing an OLEDB Connection The connection can be tested using the sample application, "Rowset Viewer" as follows: http://docs.openlinksw.com/mt/oldedbdebug.htmlCall Tracing 2008-04-09T14:37:12Z Call Tracing To turn on call tracing and enable logging to a file, use the Registry Editor (regedit or regedt32) to enter a fully qualified file name in the registry entry: To turn off call tracing simply leave this entry blank. A separate log file is opened for each process which uses the provider. Each file opened is named using the file base name specified in the DebugFile entry above with a three digit process ID suffix. http://docs.openlinksw.com/mt/oledbconinfo.htmlProvider Specific Connection Information 2008-04-09T14:37:12Z Provider Specific Connection Information OLE DB predefines a number of property sets and the properties in them. The Extended Properties property in the Initialization property group provides a means of supplying provider-specific extended connection information. The OpenLink provider supports extended properties to control: There are three ways to enter extended properties: http://docs.openlinksw.com/mt/oledbctrlodbcursor.htmlControlling ODBC Cursor Library Usage 2008-04-09T14:37:12Z Controlling ODBC Cursor Library Usage The OpenLink ODBC Provider requires that the underlying ODBC driver supports some form of scrollable cursor. In order to support OLE DB rowsets, the minimum scrolling functionality requirements include: Keyset driven and static cursors both support this functionality. All OpenLink ODBC drivers support these cursor models. However, if the OpenLink ODBC provider is to be used with a third party driver, either the driver must support one of these cursor types natively, or the Microsoft ODBC Cursor Library must be used. The latter only supports static scrollable cursors, but provides sufficient functionality to allow third party drivers to be used with the OpenLink provider. When using an OpenLink ODBC driver, it is preferable not to use the Microsoft Cursor Library. To control how the OpenLink Provider uses the ODBC Cursor Library, the provider supports the provider specific keyword “Cursors” in the ‘Extended Properties’ property string. The keyword can be set to one of three values: http://docs.openlinksw.com/mt/oledbdefbmk.htmlControlling the Default Bookmark Setting for Rowsets 2008-04-09T14:37:12Z Controlling the Default Bookmark Setting for Rowsets The extended property keyword “BookmarkDefault” controls whether rowsets are created with or without a bookmark column by default. OLE DB does not specify what the default behaviour should be. The OpenLink provider includes a bookmark column by default. Normally it should not be necessary to change this setting. To explicitly turn bookmarks on or off, use an entry of the form: BookmarkDefault=On|Off. http://docs.openlinksw.com/mt/oledbknownissuse.htmlKnown Issues 2008-04-09T14:37:12Z Known Issues These are the known issues that apply to the OpenLink OLEDB provider as of September 2005: http://docs.openlinksw.com/mt/oledbobjsints.htmlObjects and Interfaces Implemented by the OpenLink Provider 2008-04-09T14:37:12Z Objects and Interfaces Implemented by the OpenLink Provider The OpenLink provider implements four OLE DB objects. These objects, along with the interfaces implemented in the OpenLink provider, are described below.