Thank you very much for your answer, this is really show me some light
of where I might go next.

Currently, I use IBX and use many ClientDatasets and TIBQuery on the
back to access FB2.1, there is no TIBTable at all on my app.

- Do you have ClientDataset in IBO, otherwise using what component to
substitute it?

- If I convert my app. from IBX to IBO, do I need to remove all my
ClientDataset and change to TIBOQuery ? Any better way to do this ?

- How much cost for initial subscription of IBO ?
- What module that I will got with this subscription cost ?

- Any additional cost per year for renewal for example?
- What happen if we do not renewed the IBO for 1-2 years, does IBO and
my app. still working ?

I am sorry this is basic question, but I need to get advice before I
move further.

TIA

--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
> At 02:07 AM 20/12/2008, you wrote:
> >Hello
> >
> >Which one is better FibPlus or IBObjects
> >
> >- interm of speed,
>
> Probably little or no difference. Application speed is about how
you write your applications, not about which interface components you
use. Avoid "table" components, work with small datasets, don't do
"hands-off" processing by looping through sets on the client side.
>
> >supports
>
> Both have user lists. FIBPlus product developers are online for
support; with IBO these days it is mainly peer support. IBO has a
very comprehensive Help file.
>
> >learning curve
>
> Depends on previous experience - FIBPlus is easier if you used IBX
previously, IBO can be a lot easier if you used BDE previously. Like
IBX, FIBPlus makes extensive use of ClientDatasets whereas they are
not essential for IBO.
>
> The biggest part of the learning curve, whatever data access
components you use, is understanding how transactions work.
>
> All versions of IBO (including the trial version) have a
comprehensive Examples section in the installation. You can also use
the Delphi VCL data access examples with the TIBO* classes.
>
> >advantage and disavantage
>
> Depends entirely on what you need to achieve and cannot be guessed,
i.e., you can only test both and figure out which one works best for
*your* needs and abilities.
>
> >- interm of ownership price/and maintenance cost in long run which
> >product is better ?
>
> If you are only interested in basic VCL-compatible stuff, the
initial cost is higher for FIBPlus. IBO is subscription software and,
if you keep it current, the ongoing costs are approximately half of
the initial cost. FIBPlus subscriptions work in a similar way but the
subscription discounts are smaller.
>
> IBO has considerably more power for serious stuff in its "native"
series of components, if you choose that route, or plan to advance to
it. It includes its own suite of smart visual controls that are not
TDataset-compatible. FIBPlus doesn't offer an equivalent to this more
powerful series.
>
> For a current IBO subscription there are various upgrade options to
add (or bundle) the extra modules, that ensure you don't pay twice for
anything.
>
> If you need Unicode support at the client side, IBO is not ready for
it in the current release (IBO 4.8.7). I *believe* Jason and Ramil
are working on it for the forthcoming D2009 version of IBO. FIBPlus
does have some client-side Unicode support now, although not D2009 as
far as I can tell.
>
> >Sorry this is beginer question,
> >Everybody experience, I am really need your advice and thought.
>
> You need to get hold of trial downloads and try them both (in
separate projects, of course!! they are not compatible with each
other.)
>
> If you don't understand database programming with Delphi *at all*,
then Google around the Delphi sites for some tutorials (but not IBX
ones). The TDataset-compatible series of IBO (components with class
names starting "TIBO") might be an easy place to start. When using
the Delphi Helpfile, just substitute the VCL data classes with the
corresponding TIBO* ones, e.g., TDatabase --> TIBODatabase, TQuery -->
TIBOQuery.
>
> *Don't* try to mix IBX or VCL data access components with IBO ones,
or you are likely to get some unwanted libraries included. VCL visual
controls (TDBEdit, TDBGrid, etc.) and the TDatasource are just fine.
>
> hth
> Helen
>