Some query's you can't really restrict. eg. Clients - You are better to
either get all or none. Doing a count would be point less as this would
still involve doing a table scan which is slow if you have a couple of
hundred thousand records. I guess we could do
set rowcount 30 select * from Clients
but then we would get 100 support calls saying - Wheres "Joe Bloggs" (Row
31)
>Restrict your query size by date for example. Or if size is potentially
>unknown get a count before you select and if the count is too large don't
>allow the query.
No I have never tried a ClientDataSet. I have shy away from it as (I maybe
wrong) I think it would take a hell of a lot of work to change the package
(Its pretty large).
>Hi Greg. Have you tried using a ClientDataSet? If you're not familiar
>with them then I recommend looking at the Demos/MIDAS/Aggregate project
>as an initial training session. The PacketRecords property enables
>navigating exactly as you describe (records are supplied on demand, you
>dictate the rate).
Hi Kerry, yeah I think your right but it can seem like it takes the whole
dataset :)
You still working with informix at Quanta? We gave up with it and Unix and
use MS SQL
server for TrilogyLaw now.
>But, last time I checked, the BDE doesn't get "the whole dataset at
>once". As you navigate through a dbgrid, it retrieves data a page (or
>so) at a time.
>What database are you connected to?
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
