If any exceptions get thrown, then the cache gets lost.
eg If you edit a table and add several records, they could all be lost.
Ian last year posted a link to a demo using cached updates which displayed
this bug very well.
In the end we gave up and rewrote the data module using the TClientdataset
and all the problems went away.
ftp://newlook.co.nz/CachedUpdatesBug.zip
> -----Original Message-----
> From: Mark Derricutt [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, August 25, 1999 3:03 PM
> To: Multiple recipients of list database
> Subject: RE: [DUG-DB]: Cached updates and table dependancies...
>
> On Wed, 25 Aug 1999, Myles Penlington wrote:
>
> > A word of advice. If you can avoid it don't use Cached updates - There
> > is just too many bugs in it.
>
> What sorts of bugs?
>
> > Use the TClientDataset instead - I think it only comes with the C/S
> version
> > - Works like a dream by comparison and it is especially good for Master
> > Detail updates etc.
>
> Currently I'm using D4Pro, the only reason I'm using cached updates is so
> that I can let the user edit all the data on the form, and "save changes
> y/n/cancel" when they close the form. So far it all works nicely, apart
> from handling this second table.
>
> Mark
>
> --
> Mark Derricutt | Chalice of Blood
> Software Developer | New Zealand Christian Music News
> Auckland, New Zealand | http://www.chalice.gen.nz
> [EMAIL PROTECTED] | UIN: 1934853
>
> Getting jiggy with Mortification - Martyrs
>
> --------------------------------------------------------------------------
> -
> New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
