CachedUpdates should work better with IBO in many ways. There have been a
few problems with them reported where people wanted the resolution in a
different order, etc. But, other than that I am not aware of any issues with
them. They should work just great.

One thing that favors client datasets is you can let your connection drop
whereas with IBO and cached updates I have not quite got it to where it will
allow the connection to drop and then come back. I'm awfully close though...

Regards,
Jason Wharton
www.ibobjects.com

----- Original Message -----
From: "rlssv" <rene@...>
To: <IBObjects@yahoogroups.com>
Sent: Monday, January 19, 2004 5:28 AM
Subject: [IBO] Cached updates and IBO


We are going to make a new C/S application and are planning to use
cached Updates.
I have not been using cached updates for some time now. I dropped the
technique when I had bad experiences using it with Delphis std. data-
components.
So far I have only used the Tdataset-compatible components of IBO -
mainly because we are used to the std. dataaware-components and
InfoPower.
My questions are now: Are Cached Updates with the Tdataset-compatible
components as bad as with the std. Delphi.
Would it be better to skip the TDataset-compatible components and
start using the native IBO-componnents - for this reason ?

Or should I rather take a look at Delphi's Client-datasets ?
I guess your answer to the last one wil be No, but can you tell me
the advantages and disadvantages of doing so ?

Using D5, IBO 4.2.Ia

René /SSV