>Thank for the advise. However, this function does not seem to work
>at all. Therefore, I cannot incorporate it in my application
>after the most task processing function.

I thought you said that minimizing the Window resolved the memory issue (otherwise, I have no idea what "function" you are talking about).

>
>Next, how do your trigger function clear your application
>of memory leakage, maybe you can share with us.

I don't have memory issues; I was responding to your message that minimizing a window did (resolve a memory issue).

In FPW, it seemed that a CLEAR GETS would "compact memory"; though I am in no way suggesting this is appropriate in Visual FoxPro.

The bottom line is that Windows and FoxPro both exhibit behaviour that defies logic; if you find a problem and "something" seems correct the problem, then you incorporate it (no matter how bizarre) until at least the next release.

MS likes to say "we are researching the problem"; what this means is that you are on your own until hell freezes over.