Feb 1997 issue of FoxTalk had an excellent
article on How Visual FoxPro Memory useage
affects performance.

IF you can get your hands on this article I would
suggest you do it as it was an eye opener.

The bottom line is that 95 or NT does memory managing in VFP, but in FoxPro 2.x FoxPro did the
memory managing. 95 and NT are getting the
memory allotted to any session consistently wrong and
if developers do not catch this and handle it manually
your performance will be affected. The article suggests you look at the SYS(3050) function and
implement it into your code. It controls foreground
SYS(3050,1) and background SYS(3050,2) memory.

Our first attempt at VFP was a perfect example of what
memory can do to an application and we have
gleaned alot form this article.