IBProvider - news, releases, manuals

IBProvider 3.0.0.7798. The work with large volumes of data was improved.

Wed, 07 Oct 2009 00:00:00 +0300

IBProvider 3.0.0.7798. The work with large volumes of data was improved.

Optimization (v3)

The algorithms for working with the cache of rowset and the temp file were improved.

Added the new properties to initialize and rowset:

Added support of GB18030 charset (v3)

� Firebird 2.5 has a new charset � GB18030. We have added it into the list of supported charsets and included it into our automatic testing system.

New compiler

The new compiler from Visual Studio 2008 SP1 is now used for IBProvider set up, VS2005 SP1 compiler was used earlier.

New IBProvider 3.0.0.7575 with queries pool and enhanced working with Delphi.

Thu, 13 Aug 2009 00:00:00 +0300

New IBProvider 3.0.0.7575 with queries pool and enhanced working with Delphi.

Support of tables list getting in Delphi in Client Cursor Engine mode

Tables list getting has been brought into compliance with the requirements of dbGo components in Client Cursor Engine mode.

New version of Microsoft Visual C++ 2005 SP1 Runtime

IBProvider v.3.0.0.7575 RC4 uses the newer version of Microsoft Visual C++ 2005 SP1 Runtime also included into the distribution kit.

Performance optimization for repeated queries

New IBProvider v3 has the pool of SQL-queries that stores prepared and created commands and allows substantial time saving with a large number of repeated queries.

Queries pool will be especially relevant for the following tasks:

Connection to Firebird and Interbase via MS SQL Linked Server .
Client Cursor Engine (used in Delphi�s dbGo components ).
ASP applications.

Queries pool and metadata

Queries pool may prevent metadata modifications. Therefore, when DLL commands are executed the queries pool is reset to solve possible caching problems.

Queries pool operation peculiarities

Queries pool is the list that stores two types of queries:

Prepared query related to a particular SQL command. It is placed to the pool after the client has made the command's object free and started preparation of another query.
Initiated query enters the pool when the client sets incorrect SQL text and the server refuses to prepare such a query. The initiated query is placed to the pool for further use.

When the user prepares a new query:

A query with the appropriate SQL is searched for among the prepared queries. If the prepared query with the same SQL-text has been found, it is returned to the client.
If a query with the appropriate text has not been found in the pool, initiated queries are used first and then prepared queries being in the pool for over 30 seconds ( stmt_cache__req_life_time property) but related to other SQL-commands.
If the pool contains only prepared queries related to other commands and added less than 30 seconds ago ( stmt_cache__req_life_time property) or the pool is empty, a new query will be initiated and prepared.

When maximum number of queries is reached in the pool ( stmt_cache__size property), new queries start substituting old prepared queries.

Queries pool settings

Properties that manage queries pool behavior:

stmt_cache__time - minimum lifetime of an initiated or prepared query. 60 seconds by default. Any query contained in the pool for more than stmt_cache__time seconds will be deleted.
stmt_cache__req_life_time - minimum lifetime of a prepared query. 30 seconds by default.
stmt_cache__size - maximum number of resources. 1024 by default.

Queries pool disabling

Queries pool is enabled by default. To disable it, set stmt_cache__time or stmt_cache__size property as 0.

Queries pool setting via Data Links dialog

For your convenience, queries pool may be set via Data Links dialog.

Download IBProvider Professional 3.0.0.7575 RC4

* Attention! Special offer! *

20 % discount for any IBProvider license is valid for 4 days only. The time left:

To purchase IBProvider at a favorable price, you should:

select ShareIT column on IBProvider purchasing page and press Purchase near the license you have chosen.
type "bonus" in the box �Please enter your coupon code (if available)� on ShareIt partner page:

The offer is valid till midnight, August 16, 2009!

IBProvider now supports free ways of NULL-processing.

Fri, 10 Jul 2009 00:00:00 +0300

IBProvider now supports free ways of NULL-processing.

In new IBProvider release three ways of NULL processing are supported:

using special NULL flag
using type DBTYPE_NULL
using Variant with VT_NULL type

Previous versions of IBProvider support only first way of NULL-processing. If client set NULL using other ways (DBTYPE_NULL, VARIANT_WITH_NULL) IBProvider raise error conversion.

Download IBprovider Professional 3.0.0.7475 RC4 .

New IBProvider version can emulate BOOLEAN and GUID types when working with Firebird and Interbase.

Sat, 04 Jul 2009 00:00:00 +0300

New IBProvider version can emulate BOOLEAN and GUID types when working with Firebird and Interbase.

The problem is:

GUID type is currently not supported by any Firebird and Interbase server, but it is frequently used by different clients (for example, in ADO Entity Framework).
Boolean type is supported by Interbase starting from 7th version and is not supported by Firebird server. IBProvider can work with this type, but it lacks support from other servers.

The new IBProvider version supports Guid and Boolean types at driver level, and now you can freely use these types in your applications irrespective of Firebird and Interbase server versions.

Data is stored in the types supported by the server. IBProvider browsers data domains and if it finds a domain suitable by mask, it sets the corresponding Boolean or Guid in the column.

Domains should meet the following requirements:

Be based on SMALLINT type for BOOLEAN type.
Be based on CHAR(16) type with OCTETS charset for GUID type.

New properties enabling emulation of the types

To specify the data for the provider to interpret it as Bool or Guid, IBProvider has acquired two new initialization properties: user_type_boolean and user_type_guid

They define the mask for the domain representing the emulated type. The mask supports "*� and �?� symbols. The mask is case sensitive.

When these requirements are not met, the provider ignores domain name and doesn�t try to substitute the type.

Emulation works for:

Columns with a simple type;
Columns with arrays;
OUT-parameters with a simple type;
OUT-parameters with arrays;
IN-parameters with arrays.

Restrictions for emulation of the types

Due to ISC API (IB/FB) restrictions, you should explicitly specify parameter type when using simple types for input command parameters. Automatic generation of parameter description is supported for columns with arrays.

Emulation of the types in metadata

Emulation of the types also applies to metadata schemes. The provider ensures correspondence of types read at queries running and those displayed in schemes COLUMNS, PROCEDURE_PARAMETERS, PROCEDURE_COLUMNS.

The problem of connection setting via DataLink (v1,v2,v3) dialog has been fixed

We eliminated the hangup that occurred when using DataLink from the program initiating COM for working with free threaded objects.

Optimization of the provider�s objects for free threaded COM model (v1,v2,v3)

All the provider�s objects that a user can interact with provide IMarshal interface optimized for free threaded COM-applications.

Thus, now IBProvider provides maximum support for multithreaded clients irrespective of the availability of such support from gds32.dll/fbclient.dll

A good example of multistream client is IBProvider C++ test system that involves all available computer cores and processors into running half a million of provider tests.

Source texts of the test system are located in the catalogue TestCode\ActiveX\IBP\oledb_test

Finally

Application examples of the types emulation on .Net Framework: Boolean and Guid emulation in Firebird and Interbase

Download IBprovider Professional 3.0.0.7446 RC4 .

New IBProvider version has the option of cancelling commands execution and supports the new type of Firebird 2.5 queries containing SQL_NULL.

Thu, 11 Jun 2009 00:00:00 +0300

New IBProvider version has the option of cancelling commands execution and supports the new type of Firebird 2.5 queries containing SQL_NULL

Commands cancellation support in Firebird 2.5 and Interbase 6.5

The new IBProvider version has implemented the option of commands execution cancellation. The query itself and cancellation operation shall be performed in different streams.

Minimum requirements:
Server and client part Interbase 6.5 or above, Firebird 2.5 or above.

Test example on C#:
Before doing the example, run the following DLL query:

 CREATE OR ALTER PROCEDURE SP_EXEC_DUMMY_COUNTER (n integer) AS BEGIN WHILE(N>0)DO BEGIN N=N-1; END END

Example code:

 [Test(Description = "Sample - Command.Cancel")] public void CancelCommand() { using (OleDbConnection con = ConnectionProvider.CreateConnection()) { con.Open(); OleDbTransaction trans = con.BeginTransaction(); cmd.CommandText = "exec SP_EXEC_DUMMY_COUNTER(5000000)"; // call cmd.ExecuteScalar using BackgroundWorker class BackgroundWorker bw = new BackgroundWorker(); bw.DoWork += delegate(object sender, DoWorkEventArgs e) { OleDbCommand cmd1 = e.Argument as OleDbCommand; Console.WriteLine("begin call"); cmd1.ExecuteScalar(); Console.WriteLine("end call"); }; bw.RunWorkerAsync(cmd); //Cancel command after 500 miliseconds System.Threading.Thread.Sleep(500); cmd.Cancel(); // waiting while cancel perform while (bw.IsBusy) { System.Threading.Thread.Sleep(500); } trans.Commit(); } }

Test example in C++ can be seen in: TestCode\ActiveX\IBP\oledb_test\source\tso_command\ibp_tso_cmd_014_cancel.cpp

Support of new data type SQL_NULL in Firebird 2.5

Firebird 2.5 has acquired the option of running queries with expressions of �? is NULL� type. This is achieved with the help of new data type � SQL_NULL. IBProvider can process SQL_NULL for named and positional parameters.

Example:

 select count(*) from PROJECT where :par_null is NULL

If par_null parameter value is NULL, condition WHERE will be met and the command will return the number of entries in table PROJECT, otherwise the command will return 0. The following is the full text of the example in VBScript:

 dim cn, cmd, rs set cn = wscript.createobject("adodb.connection") call cn.open("Provider=LCPI.IBProvider.3;Password=masterkey;" & _ "Persist Security Info=True;User ID=sysdba; " & _ "Location=localhost:EMPLOYEE.FDB; dbclient_library=fbclient.dll") cn.BeginTrans WScript.Echo "IB Base=" & cn.Properties("IB Base").Value WScript.Echo "IB Client Version=" & cn.Properties("IB Client Version").Value WScript.Echo "Provider Version =" & cn.Properties("Provider Version").Value set cmd = WScript.Createobject("adodb.command") cmd.activeconnection = cn cmd.CommandText = "select count(*) from PROJECT where :par_null is NULL" cmd("par_null").Value = null set rs=cmd.Execute WScript.Echo cstr(rs(0)) cn.CommitTrans cn.Close

The same example on C#:

 [Test(Description = "Sample - 'is NULL' operator")] public void ExecIsNullCommand() { using (OleDbConnection con = ConnectionProvider.CreateConnection()) { con.Open(); OleDbTransaction trans = con.BeginTransaction(); OleDbCommand cmd = new OleDbCommand("select (*) from PROJECT where ? is NULL", con, trans); cmd.Parameters.AddWithValue("", null); // if cmd parameter is null then command will return count result Assert.IsTrue((int)cmd.ExecuteScalar() > 0); trans.Commit(); } }

Minimum requirements:
Server and client parts Firebird 2.5 Beta 1 or above

Access to BLOB fields from ADOExpress (dbGo) bug was fixed

Bug with BLOB fieds access was fixed. In the previous versions of IBProvider error message may appeared Write BLOB: User storage-object works incorrectly during writing BLOB data via ADOExpress (DbGo). Read details here: IB-native IN-parameter value create failed

New implementation of result sets cache

Asynchronous writing (in a separate stream) into own swap file has been implemented.
Writing into a temporary file has been optimized.

Finally

Along with implementation of support for new Firebird 2.5 options we are constantly working on the improvement of IBProvider core, implement new services that allow retaining driver�s flexibility and scalability when extending its functionality.

New IBProvider Professional 3.0.0.7270 RC4 is available for download

New IBProvider versions have the option of working with TIME type via MS SQL Linked Server and the enhanced self-descriptiveness of error messages when working with temporary files.

Tue, 05 May 2009 00:00:00 +0300

New IBProvider versions have the option of working with TIME type via MS SQL Linked Server and the enhanced self-descriptiveness of error messages when working with temporary files

New Option of working with TIME type via MS SQL Linked Server

MS SQL Linked Server requests time in DBTIMESTAMP format. Conversion from DBTIME into types containing dates has been added to IBProvider data types converter for its compatibility with MS SQL Linked Server. In this case, zero date values are recorded into Year/Month/Day fields in DATE format (1899-12-30).

This will allow to request Firebird / Interbase data in time format via MS SQL Linked Server .

Enhanced self-descriptiveness of error messages when working with temporary files.

Now IBProvider gives self-descriptive error messages related to temporary files handling.

New Firebird/Interbase driver versions are available for free downloading .

16 versions of Firebird and Interbase are now available for recording on 64-bit platforms via MS SQL Linked Server.

Fri, 17 Apr 2009 00:00:00 +0300

16 versions of Firebird and Interbase are now available for recording on 64-bit platforms via MS SQL Linked Server

Firebird and Interbase users implementing IBProvider drivers in their work last year were the first to take advantage of 64-bit applications.

We have produced two more drivers in addition to 64-bit IBProvider v3: IBProvider v2 and IBProvider v1.

Firebird, Interbase and 64-bit MS SQL Linked Server

Due to 64-bit IBProvider v2 driver, 16 versions of Firebird and Interbase are now available for recording on 64-bit Windows OS via MS SQL Linked Server.

64-bit updatable rowsets in ADO

In addition to MS SQL Linked Server, there are many libraries and utilities that support updatable rowsets technology implemented only in IBProvider v2. One of such libraries is ADO library.

64-bit support in ADO and WHS allows to develop 64-bit automation scripts in VBScript language. For example:

Firebird/Interbase database automated administration scripts;
scripts for building reports, eporting to Office, XML, sending reports via email;
database backup, recovery, and replication scripts;
customizable business logic scripts in 64-bit applications;
etc.

Using IBProvider v2 on 64-bit platforms

For IBProvider v2 to work on 64-bit platforms, you need to have 64-bit Firebird 2.1 or Firebird 2.5 client installed on the computer. You will need to rename client�s DLL from fbclient.dll into gds32.dll and copy it to system32 directory. You can also choose this option while installing Firebird client via the installer. You can download Firebird 2.1 and Firebird 2.5 here: Firebird download .

Raising stability of drivers

Insignificant errors have been fixed in the new version, including the error in KEYCOLUMN description of IColumnsRowset interface.

With IBProvider drivers, writing of applications for Firebird and Interbase will become an easy and fascinating task. We have made provision for the most difficult and will gladly share our technologies with you .

IBProvider v3 Release Candidate 4 with enhanced DDEX support and optimized working with nominated parameters. Metadata can now be accessed in user encoding.

Thu, 05 Mar 2009 00:00:00 +0300

IBProvider v3 Release Candidate 4 with enhanced DDEX support and optimized working with nominated parameters. Metadata can now be accessed in user encoding.

Improved support of DDEX (Data Designer Extensibility) when working with Firebird and Interbase

IBProvider RC4 has the new option of stored procedures calling in Visual Studio 2008 style via ODBC escape sequences . This innovation allows to create queries and TableAdapters based on stored procedures.

Data Designer Extensibility: an example of accessing: Firebird and Interbase :

Optimized working with named parameters in SQL query text:

Fewer limitations for multiple use of same named parameter in SQL query text
New algorithm for choosing named parameter data type.
Some errors of named parameters procession detected via profound testing by exhaustive method have been eliminated.

Metadata schemes and column descriptions (IColumnsRowset) support user encoding

Metadata schemes and IColumnRowset interface now consider user charset . This allows working with metadata in set encoding.

What comes next?

We continuously improve IBProvider and present new options for users with each new release. IBProvider Release Candidate 4 is the last RC of the third version.

We are planning complete substitution of IBProvider v2 functionality in the next IBProvider v3 Release:

ability to work with updatable rowsets;
support of data recording via Microsoft SQL Server Linked Server ;

Currently IBProvider v2 is the only provider that allows to update data in Firebird and Interbase Linked server. Other drivers allow only data reading from source.

IBProvider v3 RC4 is the result of 4-year innovations in data processing. It has implemented a lot of solutions and technologies, which make it completely different from other access components:

Controllable charsets processor;
SQL-parser with ODBC Escape Sequences support;
Support of 16 Firebird and Interbase versions, including Firebird 2.5 and Interbase 2009;
Automatic configuring for database server;
Ability to work on 64-bit platforms;

Combination of these two drivers will give our clients another competitive advantage for quick development of quality Firebird and Interbase applications.

Download IBProvider Professional Edition (64/32 bit)

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

Mon, 16 Feb 2009 00:00:00 +0300

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)

The brand new mechanism has been developed in IBProvider v3 for working with Firebird and Interbase text data charsets.

Mon, 12 Jan 2009 00:00:00 +0300

The brand new mechanism has been developed in IBProvider v3 for working with Firebird and Interbase text data charsets.

Changes in IBProvider v2 [build 2.6.06.2688]

Addition of UTF-8 charset support
Loading of charset information for COLUMN and PROCEDURE_PARAMETERS metadata schemes from system tables.

Changes in IBProvider v3 [build 3.0.0.6327 RC3]

New IBProvider v3 offers the brand new scheme for working with text data charsets:

We added ctype_user property that allows setting the encoding of data coming to client irrespective of the encoding in which this data is coming from database server.
Support of Firebird and Interbase charsets aliases.
We added ctype_none property that allows setting the charset for working with text data in NONE encoding.
New algorithms of BLOB fields converting provide for quick work with flowing data, optimization of interaction with ICU library.
Other important changes.

See detailed information on working with new character set processor in Firebird and Interbase charsets .

Text columns size in Firebird 2.x

IBProvider started to control text columns size when working with Firebird 2 servers in Unicode mode. If the length of loaded data exceeds the text column size the exclusion will be generated. To avoid column size checking connect in ordinary mode and set Unicode_mode=false.

Download IBProvider Professional Edition (64/32 bit)

Usage of BOOLEAN and GUID types in Firebird and Interbase.

Sat, 04 Jul 2009 00:00:00 +0300

Usage of BOOLEAN and GUID types in Firebird and Interbase.

Quick start with Borland Interbase SQL Server.

Thu, 02 Apr 2009 00:00:00 +0300

Quick start with Borland Interbase SQL Server.

Working with Firebird and Interbase in Delphi.

Tue, 02 Dec 2008 00:00:00 +0300

Working with Firebird and Interbase in Delphi.

Working with Firebird and Interbase with limited system rights.

Thu, 06 Nov 2008 00:00:00 +0300

Working with Firebird and Interbase with limited system rights.

Charsets and collations in Firebird and Interbase.

Thu, 06 Nov 2008 00:00:00 +0300

Charsets and collations in Firebird and Interbase.

Firebird Sql Server for beginners

Mon, 20 Oct 2008 00:00:00 +0300

Firebird Sql Server for beginners

Interbase and Firebird Developer's manual for ADO .Net. Part 3. Additional features: DDL, metadata schemas, ODBC Escape Sequences

Mon, 21 Apr 2008 00:00:00 +0300

Interbase and Firebird Developer's manual for ADO .Net. Part 3. Additional features: DDL, metadata schemas, ODBC Escape Sequences

Interbase and Firebird Developer's manual for ADO .Net. Part 2. Using code generators and tools of Visual Studio 2005 - VS 2008

Mon, 14 Apr 2008 00:00:00 +0300

Interbase and Firebird Developer's manual for ADO .Net. Part 2. Using code generators and tools of Visual Studio 2005 - VS 2008

10 reasons to upgrade Interbase and Firebird application to 64 bits.

Mon, 07 Apr 2008 00:00:00 +0300

10 reasons to upgrade Interbase and Firebird application to 64 bits.

Interbase and Firebird Developer's manual for Visual Studio. Part 1. Introduction to ADO .Net.

Fri, 28 Mar 2008 00:00:00 +0300

Interbase and Firebird Developer's manual for Visual Studio. Part 1. Introduction to ADO .Net.

New features of Firebird 2.0. Examples for ADO .Net (c#).

Sat, 23 Feb 2008 00:00:00 +0300

New features of Firebird 2.0. Examples for ADO .Net (c#).

Integration Services. Part 1. Import and data processing in Firebird and Interbase. (MS SQL Server 2005 Business Intelligence).

Mon, 18 Feb 2008 00:00:00 +0300

Integration Services. Part 1. Import and data processing in Firebird and Interbase. (MS SQL Server 2005 Business Intelligence).

ODBC or OLE DB? Choosing a driver for InterBase and Firebird..

Wed, 16 Jan 2008 00:00:00 +0300

ODBC or OLE DB? Choosing a driver for InterBase and Firebird..

We have published forum topic with frequently asked questions about MS SQL Server Business Intelligence.

Fri, 21 Dec 2007 00:00:00 +0300

We have published forum topic with frequently asked questions about MS SQL Server Business Intelligence.

The Compete Guide to ODBC Escape Sequences in Firebird and Interbase has published.

Tue, 04 Dec 2007 00:00:00 +0300

The Compete Guide to ODBC Escape Sequences in Firebird and Interbase has published.

We have published forum topic with frequently asked questions about MS SQL Linked Server technology.

Tue, 04 Dec 2007 00:00:00 +0300

We have published forum topic with frequently asked questions about MS SQL Linked Server technology.

Differences between IBProvider versions article was updated. Existing and new functions has grouped by categories.

Thu, 18 Oct 2007 00:00:00 +0300

Differences between IBProvider versions article was updated. Existing and new functions has grouped by categories.

New example of the storing image into the BLOB field.

Fri, 17 Aug 2007 00:00:00 +0300

New example of the storing image into the BLOB field.

Article Using new features of the Firebird 2.1 in the ADO .Net. was published.

Tue, 24 Jul 2007 00:00:00 +0300

Article Using new features of the Firebird 2.1 in the ADO .Net. was published.

New sample of using Crystal Reports with Firebird in .Net 2 (VS 2005). Download here

Wed, 21 Feb 2007 00:00:00 +0300

New sample of using Crystal Reports with Firebird in .Net 2 (VS 2005). Download here

26 and 1 samples of using ADO .Net 2.0. with Firebird 2.0. Download here

Fri, 01 Dec 2006 00:00:00 +0300

26 and 1 samples of using ADO .Net 2.0. with Firebird 2.0. Download here

New article was published: Differences between IBProvider versions

Sat, 04 Nov 2006 00:00:00 +0300

New article was published: Differences between IBProvider versions

Article How to connect InterBase database to MS SQL server and it VBScript sample was updated. Tips: using manual transaction mamagement

Wed, 02 Aug 2006 00:00:00 +0300

Article How to connect InterBase database to MS SQL server and it VBScript sample was updated. Tips: using manual transaction mamagement

IBProvider - news, releases, manuals

IBProvider 3.0.0.7798. The work with large volumes of data was improved.

IBProvider 3.0.0.7798. The work with large volumes of data was improved.

Optimization (v3)

Added support of GB18030 charset (v3)

New compiler

New IBProvider 3.0.0.7575 with queries pool and enhanced working with Delphi.

New IBProvider 3.0.0.7575 with queries pool and enhanced working with Delphi.

Support of tables list getting in Delphi in Client Cursor Engine mode

New version of Microsoft Visual C++ 2005 SP1 Runtime

Performance optimization for repeated queries

Queries pool and metadata

Queries pool operation peculiarities

Queries pool settings

Queries pool disabling

Queries pool setting via Data Links dialog

*** Attention! Special offer! ***

IBProvider now supports free ways of NULL-processing.

IBProvider now supports free ways of NULL-processing.

New IBProvider version can emulate BOOLEAN and GUID types when working with Firebird and Interbase.

New IBProvider version can emulate BOOLEAN and GUID types when working with Firebird and Interbase.

The problem is:

New properties enabling emulation of the types

Restrictions for emulation of the types

Emulation of the types in metadata

The problem of connection setting via DataLink (v1,v2,v3) dialog has been fixed

Optimization of the provider�s objects for free threaded COM model (v1,v2,v3)

Finally

New IBProvider version has the option of cancelling commands execution and supports the new type of Firebird 2.5 queries containing SQL_NULL.

New IBProvider version has the option of cancelling commands execution and supports the new type of Firebird 2.5 queries containing SQL_NULL

Commands cancellation support in Firebird 2.5 and Interbase 6.5

Support of new data type SQL_NULL in Firebird 2.5

Access to BLOB fields from ADOExpress (dbGo) bug was fixed

New implementation of result sets cache

Finally

New IBProvider versions have the option of working with TIME type via MS SQL Linked Server and the enhanced self-descriptiveness of error messages when working with temporary files.

New IBProvider versions have the option of working with TIME type via MS SQL Linked Server and the enhanced self-descriptiveness of error messages when working with temporary files

New Option of working with TIME type via MS SQL Linked Server

Enhanced self-descriptiveness of error messages when working with temporary files.

16 versions of Firebird and Interbase are now available for recording on 64-bit platforms via MS SQL Linked Server.

16 versions of Firebird and Interbase are now available for recording on 64-bit platforms via MS SQL Linked Server

Firebird, Interbase and 64-bit MS SQL Linked Server

64-bit updatable rowsets in ADO

Using IBProvider v2 on 64-bit platforms

Raising stability of drivers

IBProvider v3 Release Candidate 4 with enhanced DDEX support and optimized working with nominated parameters. Metadata can now be accessed in user encoding.

IBProvider v3 Release Candidate 4 with enhanced DDEX support and optimized working with nominated parameters. Metadata can now be accessed in user encoding.

Improved support of DDEX (Data Designer Extensibility) when working with Firebird and Interbase

Optimized working with named parameters in SQL query text:

Metadata schemes and column descriptions (IColumnsRowset) support user encoding

What comes next?

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

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

Charset markers in query text

Processing of exclusions when working with Interbase and Firebird via ADODB

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

The brand new mechanism has been developed in IBProvider v3 for working with Firebird and Interbase text data charsets.

The brand new mechanism has been developed in IBProvider v3 for working with Firebird and Interbase text data charsets.

Changes in IBProvider v2 [build 2.6.06.2688]

Changes in IBProvider v3 [build 3.0.0.6327 RC3]

Text columns size in Firebird 2.x

Usage of BOOLEAN and GUID types in Firebird and Interbase.

Quick start with Borland Interbase SQL Server.

Working with Firebird and Interbase in Delphi.

Working with Firebird and Interbase with limited system rights.

Charsets and collations in Firebird and Interbase.

Firebird Sql Server for beginners

Interbase and Firebird Developer's manual for ADO .Net. Part 3. Additional features: DDL, metadata schemas, ODBC Escape Sequences

Interbase and Firebird Developer's manual for ADO .Net. Part 2. Using code generators and tools of Visual Studio 2005 - VS 2008

10 reasons to upgrade Interbase and Firebird application to 64 bits.

Interbase and Firebird Developer's manual for Visual Studio. Part 1. Introduction to ADO .Net.

New features of Firebird 2.0. Examples for ADO .Net (c#).

Integration Services. Part 1. Import and data processing in Firebird and Interbase. (MS SQL Server 2005 Business Intelligence).

ODBC or OLE DB? Choosing a driver for InterBase and Firebird..

We have published forum topic with frequently asked questions about MS SQL Server Business Intelligence.

The Compete Guide to ODBC Escape Sequences in Firebird and Interbase has published.

We have published forum topic with frequently asked questions about MS SQL Linked Server technology.

Differences between IBProvider versions article was updated. Existing and new functions has grouped by categories.

New example of the storing image into the BLOB field.

* Attention! Special offer! *