>Try reducing VFP's "memory space" via SYS(3050); I'm convinced that some of VFP's "problems" can be traced to too much memory (handling/shuffling).
>
>Also, you might try changing the W2000 "performance settings" in Control Panel | System to "Optimize Foreground Appications" (sic).
>
>And if you're so inclined, Use the "Peroformance Monitor" to check the profiles for "Paging", "Buffering", I/O, etc.
>
>I'm embarrased to say I once traced a badly performing app to the fact that I had forgotten to turn SET COVERAGE "off" (which showed up as "writes" in Performance Monitor when all I was doing was "reading").

Win2K is better behaved than NT with severely over-allocated swap space (I run Win2K with 256MB and ~ 780MB of swap space (about 3x recommended), and VFP tries to grab between 128MB and 192MB without tweaking SYS(3050,1). Even with a lot running now (two IEs, VFP6 SP4 with a dainty little , Outlook, MSDN Help, Hacker's Guide Help) I still have 40MB of free physical RAM, with VFP6 pigging out on 85MB courtesy of a couple SQL SELECTs against a dummy table with NOFILTER. It's not VFP in the way here in all likelihood.

The P4, or the NIC, are the likely culprits.