Jos,

From all you say, I'd dive into the WIN-OS. Though I don't recognize this from W2K and up, below that it sure behaved like this. Just monitor the page-ins and outs from the OS and learn whatever there is to learn.
MS has always been out of control regarding the virtual memory. But, I'd say this was solves from off W2K. Possibly you found a situation that's still in a leak.

I thought I saw a garbage collection (SYS()) for VFP7, but now I can't find it anymore ... Supposed it's there, you might try that. When it helps, it's VFP, when it doesn't, it's the OS.

Peter


>Hi All
>
>I have a VFP7 app running under XP/NT/2K which when running uses more and more memory as time goes by. I suspect its because I am allocating (and re-allocating) some char buffers for various functions I need in a dll which requires parameters by reference.
>
>Nither RELEASE'ing the variable I am passing, the FLUSH command, nor the SYS(1104) function releases memory VFP is using. Furthermore the SYS(3050) does not limit the memory usage as advertised.
>
>However, I do notice that if you minimize the VFP app almost all memory is released except a few hundred kb. If I simulate a minimize using _SCREEN.WindowState = 1 then the same thing happens and memory is released.
>
>Question: does anybody know what internal functions VFP excutes on a minimize event to release the memory buffers? This would be very useful to know since it clearly performs far better than SYS(1104) and the like.
>
>If not is there a way to execute the _SCREEN.WindowState = 1 and then a _SCREEN.WindowState = 2 without the screen flicker :)
>
>TIA
>
>Jos