Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread Cached Updates
Fri, Feb 17 2006 3:26 PMPermanent Link

"Robert Eastlack"
I'm trying to speed up a complicated set of lookup routines when using
client/server, which are slow right now because the code iterates
sequentially (and sometimes non-sequentially) through various tables many
times.  The speed is fine when running against local data, slow when using
client/server.

I'm wondering if this would speed things up:

1. Get the lookup data using either a setrange or optimized query.  This
would usually be 300 records or less, per table.

2. Put the table into cached updates mode, which should copy the records
into a local temp table, if I understand correctly.

3. Run the procedures that loop through the lookup tables.  I'm assuming
this will be much faster because it will all take place locally.

Does anybody know of any problems with this scenario?  Is there a way to
optimize the speed when the lookup tables are first put into cached updates
mode?

Thank you for your help,
Robert


Sat, Feb 18 2006 6:38 AMPermanent Link

"Jose Eduardo Helminsky"
Robert

I am with the same problem and I had solved  it running a RemoteProcedure
(local processing) and this is much, much, much faster than C/S.

Eduardo

Mon, Feb 20 2006 12:27 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Robert,

<< Does anybody know of any problems with this scenario? >>

You should be fine with that approach.

<< Is there a way to optimize the speed when the lookup tables are first put
into cached updates mode? >>

It does so about as fast as can be expected since it uses SaveToStream
(remote) / transmit / LoadFromStream (local) internally.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image