Release of IBProvider v5

We are proud to introduce the fifth version of our basic product for working with Firebird and InterBase.

IBProvider v5 inherits all the best from IBProvider v3 and dramatically improves the quality of implementation of the OLE DB components.

For the last few years, the main development line of IBProvider was fixing problems that prevented its stable operation. First of all, we had to fix problems not related to the provider itself — we rewrote the client for Firebird and the standard pool of OLE DB connections. It took a lot of time and resourses, but it was worth it.

Now the time has come to get to IBProvider itself.

Instead of local fixes, within the support of the third version we redesigned the inner infrastructure of the OLE DB components of IBProvider taking into account the entire experience gained over the last years. In part, the ideas were taken from our ADO.NET provider.

The main qualities of IBProvider v5 are reliability and fail safety…

Read full text of IBProvider v5 release.

With Best Regards, IBProvider Team.

IBProvider 3.18. Better support of MSSQL. Changeover to the new VS 2012 compiler

We are pleased to announce the new release of our OLEDB Provider: version 3.18.

Now in your projects for Firebird and Interbase you can more comfortable work with Linked Server of MSSQL 2012. Hurrah!

In new release:

  • Improved performance of the provider as a linked MSSQL server.
  • Provider compilation with Visual Studio 2012.

Plus:

You can download IBProvider here: Firebird and Interbase driver >>>

Dozens of new options for Firebird and .NET Framework

Hey!

If you have ever worked with Firebird or Interbase using the standard .NET provider for OLE DB (System.Data.OleDb), you will have likely encountered issues like this:

  • The necessity to add ALL parameters manually.
  • Even though the OLE DB provider supports parameter generation for commands, the .NET provider doesn’t use it, so you as the programmer must do that work on your own.
  • The lack of support for named parameters. Although they actually exist, using them in reality requires a whole set of complex manipulations (the steps needed to add a parameter to a collection, etc.).
  • The impossibility of using multiple DataReader objects at the same time (Multiple Active Result Sets).
  • No execution of SQL scripts which contain several SQL expressions per command. This list of difficulties a .NET developer has to deal with is far from complete. Now it’s all different in a fundamentally new .NET Data Provider for OLE DB

IBProvider Team

Firebird driver

#AnyDAC Winter 2012 v 5.0.5 – #Delphi Components for Firebird, Interbase and more

DA-SOFT Technologies announces the availability of AnyDAC for Delphi Winter 2012 release v 5.0.5.2073 – high-speed, Universal Data Access Components for Firebird, Interbase, SQLite, MySQL, MS SQL Server, Oracle, PostgreSQL, MS Access, IBM DB2, Sybase SQL Anywhere, Informix, Advantage, dbExpress, ODBC, that simplifies the task of building Embarcadero Delphi, C++Builder and Free Pascal Compiler database applications.

AnyDAC for Delphi can be immediately downloaded from the download page.

What is new in v5.0.5 and what is AnyDAC ?

#AnyDAC Summer 2011 v 5.0.1 – #Delphi Components for Firebird, Interbase and more

DA-SOFT Technologies announces the availability of AnyDAC for Delphi Summer 2011 release v 5.0.1.1845 – high-speed, Universal Data Access Components for Firebird, Interbase, SQLite, MySQL, MS SQL Server, Oracle, PostgreSQL, MS Access, IBM DB2, Sybase SQL Anywhere, Informix, Advantage, DbExpress, ODBC, that simplifies the task of building Embarcadero Delphi, C++Builder and Free Pascal Compiler database applications.

AnyDAC for Delphi can be immediately downloaded from the download page.

What is new in v5.0.1 and what is AnyDAC ?

Firebird .NET provider and calling sp with parameters

Firebird .NET provider has ability to create parameterized queries. Both named and unnamed parameters are supported. Everything works as you expect with select, insert, delete or update commands. The tricky part comes with stored procedures. Unlike MS SQL, that has direct support for named parameters, in provider, we’re parsing parameter names and we’re sending it to server “in right order”, so developer doesn’t need to know, that internally parameters were send unnamed.

1 2