Fastreport and IBDAC 3.5 broken?

Discussion of open issues, suggestions and bugs regarding IBDAC (InterBase Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
Dokkie
Posts: 43
Joined: Wed 08 Oct 2008 21:58

Fastreport and IBDAC 3.5 broken?

Post by Dokkie » Mon 20 Sep 2010 21:58

I've upgraded my registered version of IBDAC to 3.50 today. I'm using Delphi 10 and XE.

I have FB 2.1 and IB 2009 installed.

I've updated Fastreport to 4.10 and recompiled the Demo FR4 files included with IBDAC.

Now I cannot make a connection to an existing FB database from the Data tab within FR4 using the IBDACDatabase component.

The problem is present within Delphi 2010 with a previously working report and also exists in Delphi XE with a blank report with only frxReport, frxIBDACComponents and a single IBDACDatabase component present.

In XE when I attempt to connect I get 'Unavailable database'. I can connect to the same database using TIBConnection.

Dokkie
Posts: 43
Joined: Wed 08 Oct 2008 21:58

Fastreport and IBDAC 3.5 broken?

Post by Dokkie » Mon 20 Sep 2010 22:59

Further testing suggests that IBDACDatabase component is calling GDS32.DLL by default, which is the Interbase 2009 client library - this then fails when attempting to open a database created with FB 2.1 since the ODS is not supported by Interbase 2009.

IBDACDatabase component WILL connect to a database created by IB 2009.

IBCConnection will connect to FB 2.1 or IB 2009 since it has a ClientLibrary property which allows be to set which client library to use.

It would be helpful to surface a ClientLibrary property in IBDACDatabase.

If I replace GDS323.DLL in Windows/System32 and Windows/sysWOW64 with a copy of fbclient.dll renamed to GDS32.DLL then IBDACDatabase component functions correctly. But then I lose the ability to use IB in the dataexplorer.

Dimon
Devart Team
Posts: 2910
Joined: Mon 05 Mar 2007 16:32

Post by Dimon » Thu 23 Sep 2010 15:08

Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next IBDAC build.

Post Reply