Subject Re: [ib-support] Firebird and the BDE/SQL Links
Author Helen Borrie
At 08:10 PM 08-10-02 -0400, you wrote:
>We currently have two IB 6.0 dialect 1 databases hosted on the same server
>that we're accessing using Paradox for Windows via the BDE and SQL Links. I'm
>getting ready to start a new project and I'd like to develop it using
>Firebird as well as converting the two existing databases to FB. All three
>would be running on
>the same server. We are committed to leaving the current applications and
>developing the new app in Paradox - yes, for valid reasons! The server will be
>running Windows 2000.
>
>Anyway, I have several questions about FB and the BDE that I had hoped to
>answer by experimenting, but time's running out so I'm hoping I can get the
>answers here!
>
>o There will be a transition period to move the old apps to Firebird,
>aggravated by the fact that several locations are accessing the data. Will
>the FB client
>connect to IB databases?
>
>o Can the IB6 client connect to FB?

Possibly, but it's not recommended, due to bugfixes and API additions done
to the Fb client over the past 2.25 years.


>o How does the BDE/SQL Links work with FB1? FB1.5? Is it too early to tell
>about FB2?

Not. The latest (and last) BDE driver is 5.2, which ships with Delphi
6. It has problems with both InterBase and Firebird. BDE is dead for
RDBMS support. Borland has strongly indicated that it's there for ISAM
databases only.


>o If the filename and/or registry keys for FB are different than IB's,
>will the BDE/SQL Links be able to find 'em?

Interesting question...can't answer as I've never used the BDE with Firebird.


>o Has any decision been made on how long dialect 1 will be supported in FB?

Not much longer. There's currently debate about WHEN to drop it but no
question that it will be dropped.

Quite seriously, I don't fancy your plan to use PfW for Fb or
InterBase. At best your clients will be operating on private ANSWER.DB
files, with an absolute lack of concurrency control and detachment from the
integrity constraints of the DBMS. You will be considerably worse-off than
if you stuck with Paradox. "Horses for courses".

heLen