From: "Louis Kleiman" <lkleiman@...>

> OK, I have to pile on here. Both of you should forget using the same
> component to provide both database access and editing services. You
> should use TIBQuery plus a TDataSetProvider and a TClientDataSet.
> Borland has stated quite clearly that this is their future direction.
> Plus it provides much more flexibility and control, far better
> master-detail resolution, and better performance in many situations.
>

My turn to jump in, too. <g>

It should be Borland's (or IBX's or IBO's, or Whoever's) responsibility to
provide for this underneath the architecture already provided so that the
programmer doesn't have to worry about using 3 different components just to
show an editable record on a form for a user. It's much too complicated for
new programmers to understand and makes for a disastrous upgrades to go back
and change existing applications to fit this paradigm. Can you imagine the
logic changes involved in a 120,000 lines of code, 100+ forms, datamodules
worth of program to go through and change everything? The differences
between using one TIBDataset as opposed to 3 other components to do the same
thing, albeit differently, is not small. Especially when many of the queries
are dynamically created and driven.

I just think since the if it's touted as being "the way to go", it should go
by way of the underneath architecture driving the current set of components
being used. I know that IBX is written and maintained by Jeff, not Borland,
but it's now in a very, close relationship with them since it's closed
source again.

Just thought I'd throw in my $0.02....

Woody (TMW)

----------------------
"I don't know the key to success, but the key to failure is to try to please
everyone."
-Bill Cosby