IBM Informix
Release Notes for IBM Informix OLE DB Provider
3.00.xC3DE
22 October 2007
The purpose of these release notes for IBM Informix OLE
DB Provider Version 3.00 is to:
- Describe new features in this release
- Describe any changes in old features
- Describe known problems with this release and give workarounds if any
are available
These release notes are not intended to be all-inclusive; they should be
used as an addendum to the product manuals.
The IBM Informix OLE DB Provider, version 3.00 is supported with the following
database servers:
Database Server |
Versions |
IBM Informix Dynamic Server Enterprise Edition |
7.31 and higher; 9.30 and higher; 10.0; 11.10 |
IBM Informix Dynamic Server Express Edition |
10.0, 11.10 |
IBM Informix Extended Parallel Server |
8.30 and higher |
IBM Informix OnLine |
5.10 and higher |
This section describes changes to the OLE DB Provider functionality.
Decimal Data Types without a Specified Scale
Starting with version 3.00, when the connection option (decasr8=R8) is not used for columns with DECIMAL data type and no scale
is specified, the precision and scale are evaluated by the OLE DB Provider
using the following formula for the non-ANSI databases:
DECIMAL(p) = DECIMAL(MIN(2 * p, 32),(p < 16) ? p : 12 + ((32 - p) / 4))
For best results, always specify a scale for DECIMAL data types.
This section describes the known problems with this release and how to
work around them:
- Using Visual Basic and ADO, a -206 error may get raised if DELIMIDENT
is set to 'Y' and the table name is in upper case . A case has been opened
with Microsoft to deal with this situation. As a work around, define table
names and other identifiers in lower case.
- When using the Microsoft Analysis Manager component of SQL Server 2000
the error 'Connection Failed' may be observed. A case has been opened with
Microsoft to address this situation.
- In order to display Unicode characters correctly in Visual Basic TextBoxes,
use the TextBox control found in the Microsoft Forms 2.0 Object Library.
- When a stored procedure with a return value is executed using the OLE
DB Provider, errors returned by the procedure are not returned to the application
until a fetch is called on the result set. Error information from stored
procedures with no returned values is available immediately following the
execution of the procedure.
- Known Issues with OLE/DB .NET bridge : In a .NET application, when calling
stored procedures that take no parameters, the OledbCommand attribute "CommandType"
does not function as expected. This is due to the requirement of Informix
servers to have parentheses as part of the syntax of the stored procedure
even if there are no parameters. In order to work around this use the OledbCommand's
commandText attribute to build your own string for the stored procedure call
before calling the Executexxx methods of the command interface.
This section describes the known corrections and changes that need to be
made to the IBM Informix OLE DB Provider Programmer's
Guide.
There are no known corrections or changes at this time.
Copyright IBM Corporation. 1994, 2007