>>Surely you must be joking! CachedUpdates? That creates paradox files all
>>over the show! Its a nightmare - the ultimate in fat client technology!
>>Just imagine, *WHEN* your program crashes, it leaves these MB files in the
>>client's hard disk - it soon fills up.
>
>Shurely?! :) I don't know anything about that, Dennis. I've been working
>on a project for three months now that uses Cached Updates extensively (and
>I'm not happy - it should be using ClientDataSets, but that's another
>story). It has certainly crashed multiple times during development, as
they
>do! I've never bothered clearing up any temporary files left over from
>those crashes as my machine has screeds of disk space that I'm not using.
>So one might expect that if what you were talking about was a problem, that
>there would be a _lot_ of temporary files lying around. But there aren't
>any. I scoured my drive, looked in all the likely places, and even looked
>at all the files created over the last month and there isn't even one.
Have
>I really just been extraordinarily lucky?!
>
yes, CDS is in, and Cached updates are out. You will have those files Denis
Mentioned splattered in whatever was your Default folder at the time of
crash. You can control their location by setting Session.PrivateDir := ...
I used Cached Updates for a long time and found them handy, but slow, and
the Splattered Files is Annoying, but it would take real bad design, to
entirly clog your drive - A slight over statement Denis!.
Like why are you doing selects that give such a large result set that a .Del
file could hog your entire hard disk ?????
CDS is a terrific solution I think we will see Cached Object replaced with
a New Component based on CDS technology for the Professional version
sometime in the future.
Cheers...
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
