SAS Institute. The Power to Know

SAS(R) 9.2 Providers for OLE DB: Cookbook

PDF

Known Issues for All Providers

Some ADO properties are missing in Active Server Pages (ASP) under Microsoft IIS 5.0.
When a server-side cursor is used, the following two properties cannot be accessed through the ADO interface from an ASP page:
  • "Literal Row Identity"
  • "IRowsetUpdate"
The "Literal Row Identity" property is read-only and therefore has a minor effect on the functionality of the providers. The value of the "Literal Row Identity" property is always VARIANT_TRUE.
The absence of the "IRowsetUpdate" property, however, can result in unexpected behavior. By default, the "IRowsetUpdate" property is VARIANT_FALSE, which means that recordsets are opened in immediate update mode. When recordsets are opened in immediate update mode, batch updating (via the UpdateBatch method) is not available when a server-side cursor is used.
Tip
"Literal Row Identity" and "IRowsetUpdate" are available in Visual Basic applications and in ASP pages when you use a client-side cursor. For more information about cursor types and locations, see Working with Cursor and Lock Type Combinations .
SAS customized properties cannot be accessed when you use an ADO client-side cursor with a Recordset or Connection object.
If your application uses an ADO client-side cursor, you see the following error when the application attempts to access SAS customized properties: Item cannot be found in the collection corresponding to the requested name or ordinal. This problem applies to the ADO Connection object and the ADO Recordset object. It occurs because ADO does not request information about properties from the provider when a client-side cursor is used.
To enable the application to access SAS customized properties, perform one of these tasks:
  • Use a server-side cursor location instead of a client-side cursor location.
  • Set the cursor location to server-side in order to access the SAS customized properties, and then set the cursor location to client-side.
For more information about cursor types and locations, see Working with Cursor and Lock Type Combinations .
Visual Basic DataBound Controls do not perform reliably with the SAS providers for OLE DB.
There is no resolution available. The data binding features of the Visual Basic DataBound Controls cannot be used reliably with the SAS providers for OLE DB. Do not use these controls with the providers.