Dan,

>>But I'm not so sure that "if enough of these requests come in it can slow the web server down to a crawl" is necessarily true. Your problem here is surely I/O-boundedness as opposed to CPU-boundedness. A very good I/O subsystem can do wonders in such a situation.
>>I had the luxury of working with a StorageWorks (then DEC, now Compaq, I believe) array 6 years ago and it was absolutely MARVELOUS! And imagine what improvements have been made since that time!
>
>Actually, we've found that in most cases because FoxPro is such a CPU hog, we were CPU bound not I/O bound. We purchased a box with monster drives and found we were pegging the CPU, so the disk activity was not really the problem.

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,