Known Issues for the IOM Provider

The ADO Field object "DefinedSize" property must be multiplied by 2.

For character fields, the "DefinedSize" property is set to the maximum number of characters defined for that field. Because the IOM provider returns character data as wide character strings, the size of this field in bytes is twice the value of "DefinedSize." To get an accurate size in bytes, you must multiply "DefinedSize" by 2.

Note: The "ActualSize" property correctly returns the length in bytes.

The ADO Recordset "MaxRecords" property is not available.

There is no resolution to this issue. The SAS IOM provider does not currently implement the ADO "MaxRecords" property.

Accessing a local instance of the IOM provider in an ASP page that runs under Windows 2000 Professional returns EOF.

When ASP pages that are served from a machine running Windows 2000 Professional attempt to connect to a SAS Workspace Server on the same machine by using COM, all Recordset objects will report EOF immediately after being opened as if the recordsets contain no rows. This behavior occurs only under Windows 2000 Professional. You do not encounter this problem when the ASP page server and the SAS Workspace Server are on different machines.

As a workaround, use the dcomcnfg tool to change the "Authentication Level" of the "SAS: IOM DCOM Servers" to "(None)". For more information about using dcomcnfg, see Turning Off Call Security in the Microsoft Developer Network Library at http://msdn2.microsoft.com/en-us/library/ms687216.aspx.

Move methods fail if you use them to access V7 compressed data sets.

The following ADO Recordset methods will fail with Version 7 compressed data sets when the number of records to move is nonzero: Move, MoveNext, MoveFirst, and MovePrevious. In this situation, these methods result in random access operations, which are not supported in compressed SAS data sets before Version 8.

In SAS Version 8, when a compressed SAS data set is created with the options POINTOBS=YES and RESUSE=NO (the default values), the data set can be accessed randomly, and the Move, MoveNext, MoveFirst, and MovePrevious methods are successful.