If it talks too long to go to the bottom then you are letting the users
query too much data.
This illustrates a fundemental design problem of C/S applications that
Delphi goes a long way towards solving, but not completely.
Basically, the golden rule is don't uses grids, which is what I suspect you
are doing. If you must, then limit the amount of data the user can view
with one query.
I always display an empty form first. The users must search for something
(or add. I use a grid for navigation of the search results but the search
is done on the server and I can control how many records get returned to the
client - and the content.
Another idea is to return jsut enough information to identify the record to
the user and then do a seperate request for the remainder of each record.
In your case, jsut seperating the blob into a seperate request may do the
trick.
>From: Yanbo Li <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
>Subject: [DUG]: CORBA Client
>Date: Tue, 3 Aug 1999 11:18:35 +1200
>
>Hi there,
>
>I have written a CORBA database application, it works fine except one
>problem.
>
>In client application, if ClientDataSet is big, and contains BLOB field.
>Call ClientDataSet.Last takes a long time. The reason is client app
>cashes in all the table/query data, in the memory.
>
>Can any one point out the tricks to cash in only the last packet while
>calling Last?
>
>Thanks
>Yanbo
>
>
>---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
