<?xml version="1.0" encoding="ISO-8859-1" ?>
<rss version="2.0">
 <channel>
  <title>OLE-DB Client Provider</title>
  <link>http://docs.openlinksw.com/st/oledb.html</link>
  <description>OpenLink Lite Documentation</description>
  <managingEditor />
  <pubDate>Wed, 25 Apr 2012 15:29:52 GMT</pubDate>
  <generator />
  <webMaster>webmaster@openlinksw.com</webMaster>
  <image>
    <title>OpenLink Lite Documentation</title>
    <url>http://docs.openlinksw.com/st/../images/lite/misc/logo.jpg</url>
    <link>http://docs.openlinksw.com/st/oledb.html</link>
    <description>OpenLink Lite Documentation</description>
  </image>
  <item>
    <guid>http://docs.openlinksw.com/st/oledbtest.html</guid>
    <author />
    <category>Testing an OLEDB Connection</category>
    <link>http://docs.openlinksw.com/st/oledbtest.html</link>
    <pubDate>Wed, 25 Apr 2012 15:29:52 GMT</pubDate>
    <title>Testing an OLEDB Connection</title>
    <description>The connection can be tested using the sample application, &quot;Rowset 
    Viewer&quot; as follows:

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/st/oldedbdebug.html</guid>
    <author />
    <category>Call Tracing</category>
    <link>http://docs.openlinksw.com/st/oldedbdebug.html</link>
    <pubDate>Wed, 25 Apr 2012 15:29:52 GMT</pubDate>
    <title>Call Tracing</title>
    <description>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.

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/st/oledbconinfo.html</guid>
    <author />
    <category>Provider Specific Connection Information</category>
    <link>http://docs.openlinksw.com/st/oledbconinfo.html</link>
    <pubDate>Wed, 25 Apr 2012 15:29:52 GMT</pubDate>
    <title>Provider Specific Connection Information</title>
    <description>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:

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/st/oledbctrlodbcursor.html</guid>
    <author />
    <category>Controlling ODBC Cursor Library Usage</category>
    <link>http://docs.openlinksw.com/st/oledbctrlodbcursor.html</link>
    <pubDate>Wed, 25 Apr 2012 15:29:52 GMT</pubDate>
    <title>Controlling ODBC Cursor Library Usage</title>
    <description>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:

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/st/oledbdefbmk.html</guid>
    <author />
    <category>Controlling the Default Bookmark Setting for Rowsets</category>
    <link>http://docs.openlinksw.com/st/oledbdefbmk.html</link>
    <pubDate>Wed, 25 Apr 2012 15:29:52 GMT</pubDate>
    <title>Controlling the Default Bookmark Setting for Rowsets</title>
    <description>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. 

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/st/oledbknownissuse.html</guid>
    <author />
    <category>Known Issues</category>
    <link>http://docs.openlinksw.com/st/oledbknownissuse.html</link>
    <pubDate>Wed, 25 Apr 2012 15:29:52 GMT</pubDate>
    <title>Known Issues</title>
    <description>These are the known issues that apply to the OpenLink OLEDB provider as of 
     September 2005:

</description>
  </item>
  <item>
    <guid>http://docs.openlinksw.com/st/oledbobjsints.html</guid>
    <author />
    <category>Objects and Interfaces Implemented by the OpenLink Provider</category>
    <link>http://docs.openlinksw.com/st/oledbobjsints.html</link>
    <pubDate>Wed, 25 Apr 2012 15:29:52 GMT</pubDate>
    <title>Objects and Interfaces Implemented by the OpenLink Provider</title>
    <description>The OpenLink provider implements four OLE DB objects.

These objects, along with the interfaces implemented in
      the OpenLink provider, are described below.

</description>
  </item>
 </channel>
</rss>


