So, I have a database -- about 40000 records.

I have a script that walks through the database and changes a value of
one of the fields.

Then it sorts the entire database by a different field.

If I run this on my desktop -- G5/2.3/DP/1.5G RAM -- it takes about 45
seconds to run this script under FileMaker 8 Client.

If I put this database up on my FileMaker Server (xserve dual 2.0G/1G
RAM), it takes about 3:10 to run this script.

Granted, my desktop is a much faster machine, but is it normal for this
discrepancy in speed between client/server? Seems rather severe
increase in time (5 fold, almost...)


(I *should* mention that it took about 4:10 to run the same script
under FileMaker 7 Server/Client, so 8 Server/Client is faster than
7...)


Thoughts?

- Steve

In article <171020051700057073%maser (AT) umich (DOT) edu>, maser (AT) umich (DOT) edu says...
This is generally much faster to do via a "replace by calculation" than
a looping/set field.

Its not really abnormal for their to be a discrepency, particularly in
the large looping scenario you presented.

For what its worth, why do you need to change a field in every record in
the database with any frequency? Usually there's a 'better way'...

-regards,
dave

In article <MPG.1dbdc71585f21e09989d79 (AT) shawnews (DOT) vf.shawcable.net>, 42
<nospam (AT) nospam (DOT) com> wrote:

For what its worth, why do you need to change a field in every record
in

Primarily, I was doing this just to drive things as a "speed test" --
knowing full well that it was a slow way to do this

- Steve