>We have a customer who needs to store and report on large data tables (650MB - 1.5GB)...we recently needed to re-index one of these tables and for some reason it took days to do - even though they run a dedicated PIII with a dual processor and heaps of RAM. Their Windows NT person said something about VFP not using the "paging file" very effectively hence the long processing time.

Their Windows NT person doesn't know very much about how how paging works in NT. This is for the most part entirely under the control of the OS. There are things one can do in a Win32 app to help avoid page faults (which are very expensive when it comes to clock cycles), but VFP does not control the page file directly.

>Does anyone know anything about how VFP utilises paging files, and if there is a way we can speed up this process??

Play around with SYS(3050). Even on my 2Gb RAM server, VFP doesn't take up a whole lot of memory by default. Oh, and having to processors won't make any difference, VFP is single-threaded.