Devart Forums

We have experienced problems when using IBDAC components with FB 2.0 as described in http://forums.devart.com/viewtopic.php?f=24&t=30777, and see the need to upgrade to FB 2.5.
Upgrading on platforms hosting our application is easy enough, but connecting to databases on remote server locations uses the firebird service installed on the given server, not our host platform.

To address this issue we want a check on creation of the TIBCConnection object, getting the Firebird version used to enable the connection (the firebird version running at the location of the database). We have found the DatabaseInfo.FBVersion property on the connection but testing has shown this does not give us what we want. Is there a property that gives us what we need?

If all else fails, we can obtain one of the queries that would fail with older firebird versions and run it, but a more elegant solution would be preferable

Please clarify, why using of the TIBCConnection.DatabaseInfo.FBVersion property is not suitable for you?

ViktorV wrote:Please clarify, why using of the TIBCConnection.DatabaseInfo.FBVersion property is not suitable for you?

I've experienced a situation where the TIBCConnection.DatabaseInfo.FBVersion shows some unexpected results.

I ran the following test scenario:
1) uninstall current firebird service
2) install firebird service x
3) run a small application in which I establish an IBCConnection and verify the FBVersion.

Here's where it gets hairy: On the computer I used the FBVersion was not shown to be service x as expected, but the old, now uninstalled, service. I concluded that something was out of order and contacted you.
I've now done the same test on a different computer and everything seems to be in order, so I went back to the original machine and verified the unexpected behaviour. Then I uninstalled FB altogether and tried running the application, yielding the expected 'unavailable database' exception. After reinstalling FB version x, the FBVersion showed the correct firebird version..

We are glad to see that the issue resolved. Please contact us if any further questions concerning IBDAC usage come up.