Sergey,

I agree that the number of handles reported by VFP does not change much (+/- 1) and the amount of allocated memory reported by VFP doesn't change much either. But, the amount of memory that Windows THINKS VFP has allocated to ir changes a lot. You cannot see the problem from inside VFP. You have to monitor the process with a tool such as Process Explorer to see it. It may not be VFP at all that has the leak. The leak may be in Window's memory handling routines and VFP may be using those routines in such a way that this problem shows up under certain circumstances. If I am right, this may have big implications for VFP solutions that run perpetually under just the right setup.

Try Process Explorer and see what you think. I wish there were some tool that could see inside a processes and that could export the statistics continuously out to a disk file if needed.

Thanks again Sergey.

Steve