>Dan,
>
>snip<

>Pulling 25.000 records from the network should not be due to running out of CPU resources. Like Jim says, There should some I/O problem causing the slow response. You've tried the SEEK, COPY WHILE .. FOR .. method which rules out rushmore optimization problems. The problem should be network or other I/O problems. Did you try this on your local machine or on a network station ?
>
>Walter,

I don't know what to tell you. I've tried all of these tests on my local machine. I was actually hoping that, even though it was an x-base solution, it was going solve my problems.

I've also tried this on a machine with dual P4s locally. It always takes about 20 to 25 seconds.