Unfortunately, like the rest of Delphi, cached updates is not very well
documented. I got on to cached updates a few years ago when I had problems
with Paradox table corruption. I was in contact with an engineer from
Borland Oz, who asked if I used cached updates - and advised against it. It
was in my conversation with him that I learnt that cached updates uses
Paradox tables. Later experimentation showed that they indeed do. One can
then deduce that for cached updates to work, the BDE is needed.
This is all irrelevant now, because I heard that BDE in the next version of
Delphi will be driven by a drawing engine. It must be Friday.
Regards,
Dennis.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Terry Johnson
> Sent: Thursday, 6 April 2000 20:18
> To: Multiple recipients of list delphi
> Subject: RE: [DUG]: ADO & Cached Updates
>
>
> Thanks Dennis. Is this stuff written down anywhere? I wasn't
> aware of the
> implementation... the documentation hardly goes into much
> detail on the
> 'how'.
>
> Cheers,
> Terry
>
> >
> Terry,
>
> I hope you realise that cached updates requires BDE (because
> it stores the
> cached data in Paradox files). That being the case, why not
> just stick to
> BDE / ODBC to get to SQL server? IMHO, ADO is only useful if you can
> eliminate BDE from your install. If you use it in addition
> to BDE, you
> have
> one super fat install!
>
> Regards,
> Dennis.
> <
>
> --------------------------------------------------------------
> -------------
> New Zealand Delphi Users group - Delphi List -
> [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
