| Subject | Accessing IB from Delphi |
|---|---|
| Author | Doug Chamberlin |
| Post date | 2000-07-05T14:18:14Z |
At 7/5/2000 10:02 AM (Wednesday), Jani Soderhall wrote:
have some details missing. Perhaps we can turn this thread into a FAQ when
done.
1) Borland Database Engine components (BDE)
Can help you client code to be very portable to other databases if you pay
attention to portability issues. Lower overall performance with IB. Some
really awful performance if you make one of several common access mistakes,
such as using TTables. Some of the IB native capabilities which are beyond
the basic INSERT/DELETE/UPDATE/EXECUTE STORED PROCEDURE set are not
available via BDE.
Some questions about future support for BDE from Borland but that is
nothing new.
2) Interbase Express components (IBX)
These component are specific to IB and only are available for Delphi 5.
There is an update to the versions which come with Delphi 5 available from
the IB web site. Class hierarchy is similar to BDE but not quite the same.
Faster performance than BDE. Some of the native capabilities are available
via IBX such as the services API. Source will be open sourced along with IB 6.
3) Interbase Objects (IBO)
Comprehensive library of access components which tap just about every
native IB capability. Organized somewhat differently than the above class
libraries so a steeper learning curve but many say well worth the effort.
Definitely the way to go if you are a committed IB enthusiast. Dedicated
community of developers available to help you make it work. Fast access to IB.
Free for non-commercial use. Reasonable access to source code. Reasonable
licensing policy.
4) Native IB API
Build your own access direct to IB through the published API. Only viable
for die-hards since IBO and IBX both are built on top of the same API. Why
reinvent the wheel?
>I see this discussion taking off in the direction of "what's the best way toThere are four possibilities I see. I have not tried every one so I may
>connect to Interbase from Delphi" and I would like to know what opinions are
>out there on the use of the IB Express components shipped with Delphi.
>
>IBObjects often receives good reviews, but are IB Express (apparently based
>upon IBO) any better, equivalent, or worse?
>
>Having already started using IB Express components is it worth having a look
>at others?
have some details missing. Perhaps we can turn this thread into a FAQ when
done.
1) Borland Database Engine components (BDE)
Can help you client code to be very portable to other databases if you pay
attention to portability issues. Lower overall performance with IB. Some
really awful performance if you make one of several common access mistakes,
such as using TTables. Some of the IB native capabilities which are beyond
the basic INSERT/DELETE/UPDATE/EXECUTE STORED PROCEDURE set are not
available via BDE.
Some questions about future support for BDE from Borland but that is
nothing new.
2) Interbase Express components (IBX)
These component are specific to IB and only are available for Delphi 5.
There is an update to the versions which come with Delphi 5 available from
the IB web site. Class hierarchy is similar to BDE but not quite the same.
Faster performance than BDE. Some of the native capabilities are available
via IBX such as the services API. Source will be open sourced along with IB 6.
3) Interbase Objects (IBO)
Comprehensive library of access components which tap just about every
native IB capability. Organized somewhat differently than the above class
libraries so a steeper learning curve but many say well worth the effort.
Definitely the way to go if you are a committed IB enthusiast. Dedicated
community of developers available to help you make it work. Fast access to IB.
Free for non-commercial use. Reasonable access to source code. Reasonable
licensing policy.
4) Native IB API
Build your own access direct to IB through the published API. Only viable
for die-hards since IBO and IBX both are built on top of the same API. Why
reinvent the wheel?