Thanks Claude, I appreciate!

Fernando

>The problem is that vfp will grab as much memory as possible for whatever it's doing. I don't think it was a problem on early OSs, but, became one starting with NT and on through XP. This is mostly a problem in long-running batch-type jobs. Setting the application to 1/3 of total memory lets the application and OS live in better harmony in long-running jobs.
>The actual formula comes from an old performance tip in a Microsoft White paper on fine tuning VFP performance. It's probably still on the MS site somewhere...
>>Hi Claude,
>>
>>Pardom me for jumping in.
>>
>>Otherwise, a memory hog can be taken care of with SYS(3050, 1, VAL(SYS (3050, 1, 0)) / 3), especially on Win2k/WinXP ...
>>
>>I'm really concerned with problems regarding CPU and memory utilization of VFP apps. Yesterday I openned a thread #871717, to get some information about that.
>>
>>I'm trying to understand SYS(3050), SYS(1104) as well as any Windows API calls that deals with that subject and can be used to acomplish those tasks I'm wanting to (limit the amout of memory used, improve execution performance and the like).
>>
>>Could you please tell me what's behind of:
>>

>>SYS(3050, 1, VAL(SYS (3050, 1, 0)) / 3)
>>

>>As I could understand, you're seting the foreground buffer memory size to 1/3 of the returned maximum amount of memory Visual FoxPro allocated for the foreground buffer. Is it that? If so, what's the involved logic?
>>
>>Thanks!
>>
>>Fernando