> Actually, FIBPlus is not similar to IBO. They have different
> class ideology and structure,

Agreed.

> because IBO has been projected for Delphi 2, which had not an
> abstract TDataSet. The current IBO model is an effect of this.
> FIBPlus was oriented on TDataSet paradigm from the very beginning,
> that is why we do not need our own visual components and can use any
> third-party ones. May be it is the reason for IBO price - you buy a
> lot of components but will you ever use them?

Perhaps the Delphi2 issues were the original justification for the
separate heirarchy of dataset components and associated controls,
however there is much more to it than that now.

I dont want to get too far off topic for this list, but do want to
highlight that for many of us the alternate components (we refer to
them as "native IBO") are the preferred components to use. They offer
many features not provided by the TDataset stuff and can save huge
amounts of code. There are also many useful tools offerred in the IBO
collection.

Also note that the price being mentioned is for a bundle, you can pick
and choose modules and so bring the price down to be much more
comparable when purchasing just the equivalent components of other
libraries.

--
Geoff Worboys
Telesis Computing