--- In ib-support@y..., Helen Borrie <helebor@d...> wrote:

> At 07:16 PM 15-01-02 +0000, serg_vostrikov_dr wrote:
>
> > Actually, FIBPlus is not similar to IBO. They have different
> >class ideology and structure, because IBO has been projected for
> >Delphi 2, which had not an abstract TDataSet. The current IBO

model

> >is an effect of this.
>
> In a way, you could say that...because, before Delphi 3, there were

aspects of the Paradox database engine that you could not escape from
because the TDataset wasn't virtual.
I know this, thank you very much :)

>
> After D3, it became possible to wrap the "native" IBO architecture

around a TDataset descendant and thereby provide compatibility with
the VCL components + emulation of the logical model that the BDE
provided. A TDataset descendant on its own (FIB, FIBPlus, IBX) can't
encapsulate that, even today.

The fact is that we do not try emulate BDE because this model is
not effective in client/server applications. And I doubt that we will
emulate it in future. I understand IBO policy: at the beginning it
should emulate BDE to entice customers, which used BDE. Great idea
for that time. But not for now! On my opinion, BDE emulation is
emulation of dead product. Actually Borland does not develop BDE
intensively. It prefer other ways :), and it is right!

All professional, which working with Interbase/Firebird/Yaffil (do
you know about Yaffil?), try to use in their application special
Interbase features. Thus they do not use BDE emulation and any direct
db-engine (like IBD, FIBPlus, etc) is the way for them to avoid BDE
approach. If you agree with it you should make a conclusion that BDE-
emulation is not an advantage :)

> Instead of calling methods and setting properties, you have to

write custom code handlers in every application.
Please, do not tell such things without details, because it is not
fairy. I do not say anything about IBX, but regarding FIBPlus your
information is wrong. You know that nobody can write his/her code
without event-handlers at all, because components creator can not
write all code by himself/herself. However we automize a lot of
standard developer's tasks. We demostrated on Interbase RoadShow in
Germany full functional examples without delphi code at all.

>
> The "current IBO model" is two distinct sets of component classes.

The TIBO* classes are functionally equivalent to FIB, FIBPlus and
IBX, meaning that you can build BDE-like applications with them
I'm sorry, but using TDataSet-classes is not building BDE-like
applcations. This is VERY important thing. BDE is not equal TDataSet
approach. TDataSet approach is only a way of visual data
presentation. BDE is a mechanism of transaction control, session
organization, etc. You can use TDataSet descendants and not use BDE
model.

> and you use the native VCL and TDataset/TDatasource-compatible

controls and data-aware components with them. But you also get
access to some important native IBO properties and methods, session
control, global property and attribute setting, OAT management and so
on;
I agree. But using other engines you get access to some important
native 'other engines' properties. :) It is the same.

> and the native IB_Connection is embedded in the database component,

enabling you to add multi-transaction and multi-database capability
too. It also means you can use the unbuffered cursor and DSQL
components in your TDataset-compatible applications.
You know about FIBPlus TpFIBquery or IBX TIBSQL. They are
unbuffered cursors and developers can use it without limits. It is
the same too.

>
> The "native IBO" classes - those with the TIB_* prefix are the

fully VCL-independent ones, which have their own controls (70 or so
at last count).
This is really important thing. On my opinion creation of visual
components is an absolutely defferent task than creation of db engine
components. Moreover, all of us know about great visual components
and Report Builders (DevExpress or FastReprot, for example). By the
way, why IBO does not contain native IBO report components? If
consider IBO visual components more effective then IBO MUST contain
its own report builder components.
I understand that creation of own visual components was only the
way to add direct Interbase API support to Delphi. But it was correct
for Delphi 2, now we have Delphi 6. Using native IBO visual
components, I think, is not very good, because developer do not get
modern visual capabilities. I hope you will not compare functionality
DevExpress and IBO controls?

> A single FIBPlus licence costs $99 US.

Actually, not it costs $ 199

>If you want only the IBO TDataset compatibility, you spend $149.50

for the IBO TDataset-compatible module (which actually includes a
TIBOTransaction component, so you can have multiple transactions even
if you just buy this module).
What about services API, non-buffered queries, some special features?

>
> So IBO is 25% cheaper than FIBPlus if you compare apples with

apples...
No apples :). The core FIBPlus features are oriented on TDataSet
support in contrast to IBO. So if you purchase FIBPlus you get
EVERYTHING. If you purchase IBO Dataset-compatible module you get
only a part of functionality. I do not mean visual contols, of course.

>
> I didn't want to raise these "price war arguments" but you did!

And the record needed setting straight, didn't it? :)
Of course :)

>
> Seriously, I think it's a mistake to choose connectivity on the

basis of price alone.
Price is only one of reasons, I'm sure.

> You should seriously evaluate them against your own requirements

and their likely cost of ownership. Consider aspects like which
editions of Delphi you have to buy, in order to use them (e.g. you
can develop with native IBO using Personal edition!),
The same is for FIBPlus :) if we are talking about Delphi 3-5
Standard/Desktop Editions. Unfortunately, Delphi 6 Personal does not
support FIBPlus, it is a fact. However, I told, professional tools
should use professional visual solutions. I do not want to say that
IBO visual control are not professional, but you agree that visual
components are not the most important part in IBO.

--
Sincerely yours,
Serg

Devrace - software for developers!
__________________________________
e-mail: sv@...
url : http://www.devrace.com/
http://www.fibplus.net/
http://www.athlant.com/