IBProvider v1.6.1.185

1. DBTYPE_NUMERIC support
   • The conversion between other data types (numeric/string/VARIANT) is implemented)
   • The InterBase NUMERIC/DECIMAL data types are represented as DBTYPE_NUMERIC now
2. Correct presentation of TIMESTAMP (IB6) and DATE (IB4/5). The truncation of the tenth fractions of milliseconds is removed. DBTYPE_TYMESTAMP is used for these date formats.
3. The PRECISION and SCALE values in the description of columns and parameters are reduced to the requirements of the specification.
4. The possibility of setting of all properties of connection by «Extended Properties» value.
5. New informative property «Provider Friendly Name».
6. New property of initialization and rowsets «truncate_char». Its default value is «true».
7. New set of information schema TABLES_INFO.
8. The defects in forming of contents of the information schemes are eliminated.

The only important change is the inclusion of DB_NUMERIC support, as there is a large size of the code connected with converting. We recommend to check up the reliability of received and passed NUMERIC and DECIMAL data types. Despite of careful check and testing of the code on our part, you should better be reinsured. The registered users can independently check up the code, as it is common with C++ client to OLE DB providers.

The usage of the IBProvider as linked MSSQL server

Since the version 1.6.1 IBProvider can be used as the supplier of the information for use in Microsoft Distributed Query. During testing the following things were revealed:

• At registration of the data source, it is better to allow loading in the process of the server «Allow InProcess». Otherwise provider will be started in the separate process. We were able to work thus only when registered in the system as the administrator.
• The connection string should look like thus: «…;free_threading=true;truncate_char=false;…» It indicates provider, that it should declare about the support of «free threading» and prohibits to it the truncation of tail space characters, as MSSQL verifies obtained data with the description of columns. In the connection string it is not necessary to indicate «auto_commit=true»;
• Before execution of query it is necessary to execute the command begin transaction It results that the IBProvider data source will be connected to the coordinator of disrtibuted transactions. Otherwise the well-known error will happen: «Automatic transaction is disabled»;
• When working with the Database of the 3 dialect it is necessary to indicate upper and lower case correctly, as MSSQL begins to use «» when passing the names. At connection to IB4/5 or explicit indication «dialect = 1» the case can be ignored.
• Range of dates IB and MSSQL do not coincide. Therefore check up, that in the tables participating in queries there are no dates below January 1, 1753.
• In queries it is impossible to use the tables the containing arrays. MSSQL does not understand them.
• Since IBProvider at the present moment does not realize support of updated rowsets, the execution of queries of data modification (insert/update/delete) is yet impossible. At least, we were not able to execute these operations.

The testing was realized on MSSQL 7.0.623.