Hey Jim!

How's things!

Its my understanding that VFP will request large amounts of memory and the OS will attempt to provide it by swapping other stuff out. Gary DeWitt(spelling?) used GlobalMemoryStatus IN Win32API to determine the available memory and then set sys(3050) to fit within the remaining memory.

>Christof,
>
>In the second paragraph below, are you saying that VFP is taking into it's own hands what the OS should do for an application???
>Seems doubtful that some VFP code would be more 'optimized' for this purpose than the standard OS code, especially in the later releases. Especially given the variety of places that VFP's own TEMP directory could be placed.
>
>
>
>>Hi Renoir,
>>
>>Are you running Windows NT/2000/XP? In this case you really should get FileMon from Sysinternals (http://www.sysinternals.com/ntw2k/utilities.shtml). It monitors all file activity including read and write operations. Maybe the log explains what happens.
>>
>>Also, make sure you check SYS(3050). This buffer is used for caching all temporary data. If VFP needs more memory than you allow, VFP starts swapping to its temp directory. If this happens to be on the server or on a slow drive, this could slow down the query considerably.
>>
>>Christof