>>do not forget that vfp may allocate memory as well while your program is running , eg for variables
>
>Sure.
>
>The tests are not run in situ within a large applcations but as standalone test routines. I'll implement this putfile replacement very carefully when we have confirmation that it is rock-solid.
>
> I just made a last manual test. Running a very plain test - 2 000 calls of the dialogbox - the memory use moves from around 3.5 MB, plain vfp interactive session with zero addition, to nearly 50MB. The only way to clear the memory use "Quit"....


Haha,

And how many variables were created, assigned and destroyed ?

That is not my understanding of a memory leak

If you want to be sure, have a look at the code, each malloc() has to have its free()

You can also replace malloc() with HeapAlloc() and free() with HeapFree()

>Well 2 000 "save as..." action call is not your standard user activity:-)
>
>Daniel