New IBProvider allows comprehensive work in Unicode applications, enhanced work with NONE encoding, and supports charset markers.

New IBProvider v.3.0.0.6600 RC3

  • All the detected problems that prevented comprehensive work with Firebird and Interbase from UNICODE applications have been eliminated.
  • Supports charset markers in SQL queries.
  • Supports exclusions processing when working with Interbase and Firebird via ADODB.
  • Supports working with database object names containing national symbols for connections with NONE charset.
  • Enhanced work with metadata schemes when working with database via NONE charset.
  • Advanced testing allowed detection and elimination of errors.
  • ISO8859_15 charset support.

IBProvider has implemented the unique support of your database text data and presents very simple but flexible provider setting scheme to meet specific requirements of the client.

Detailed information on encoding processor setting: Firebird and Interbase charsets.

Charset markers in query text

IBProvider v3 have learned to process SQL queries containing charset markers.

Charset markers allow to transform individual text fields into specified encoding. They are used at data transfer to server. Example of a query with markers: 


insert into TEST_TABLE values(_unicode_fss'unicode_text', _win1251'ðóññêèé òåêñò')
  • 'unicode_text' will be transferred to server in UNICODE_FSS charset.
  • 'ðóññêèé òåêñò' will be transformed into WIN1251 encoding.

Processing of exclusions when working with Interbase and Firebird via ADODB

After the new scheme of working with exclusions had been implemented in the latest releases, processing of errors was not supported at working with Firebird and Interbase via ADODB. This was due to undocumented interface code-named IDBPrimaryError, which has been successfully implemented in the new release.

Support of working with database object names containing national symbols for connections with NONE charset

When connecting to Interbase or Firebird database without charset specification, object names in double quotes in a SQL query will be transformed into UNICODE_FSS charset. This ensures correct work with objects, which names contain national symbols (not ASCII), for example, Russian letters. For example:

Select “ÑÒÎËÁÅÖ1” from “ÒÀÁËÈÖÀ1”

Download IBProvider Professional Edition (64/32 bit)