Xavier et al,

You have encountered a bug in VFP that has been around since the first version of FPW. I have hit this problem (the memory leak) in every version that we use for our application (FPW2.5 thourgh VFP6.0). If you check the MicroFlacid(oops, I mean MicroSoft) web site for current bugs you will find this one. They keep saying that they fix this issue, but it never happens. I guess its either not that important or too difficult for the vfp team to fix.

...douglas
ps -In fact, I will paste the information here:

BUG: Previewing Report Writer Causes Memory Leak

The information in this article applies to:
Microsoft Visual FoxPro for Windows, versions 5.0, 5.0a, 6.0

SYMPTOMS

Issuing a REPORT FORM FormName PREVIEW causes Visual FoxPro to leak one memory handle each time you close the Preview window.


STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. The Visual Studio 6.0 Service Pack 3 readme erroneously lists this bug as being fixed. Service Pack 3 did not fix this bug.


MORE INFORMATION

Steps to Reproduce Behavior

1.Create a report, called mytest, containing a label in the Detail line saying "Test." (This is not a field from a table.)

2.Open the Employee table and place the following code in a program and run it:

FOR i=1 to 10
? SYS(1011)
REPORT FORM mytest.frx PREVIEW
NEXT

3.Run the program.

4.When the Preview window appears, close it.

As the code runs, the notice that the number of memory handles increases by one after the first few iterations of the For..Next loop. The problem occurs regardless of whether you close the window using the Close button on the toolbar or the Close box of the Preview form window.

The SYS(1011) function is used to determine how many memory handles are being used up by a process within FoxPro. This is an undocumented SYS function.