Hi,

I'm wanting to limit the total memory used by a VFP app to a certain amount, let's say 64Mb.

While searching the messages area got to thread #686349 (SYS(3050) memory buffer size). In message #686371 Sergey Berezniker suggests to take a look at FAQ ID: 8125. Next in message #686896, Christof Lange says gives some interesting information on an app behavior when changing memory settings.

On the other hand, in thread #728197 (SYS(3050) Not Respected According to Task Manager) Scott McDaniel ends asking "Does anyone know why Visual FoxPro would ignore these settings?".

In message #728231 (in the same thread) Christof Lange says: "SYS(3050) only controls a memory block called the "page pool". It's basically the cache used for data operations. See KB article Q136694 for details.".

and ends saying:

"Visual FoxPro has several other memory blocks. For one, it has to reside somewhere in memory itself. Then, there's the "handle pool" memory. This keeps all the variables, form, menus, popups, etc. The "handle pool" is only limited by the virtual memory and cannot be limited in our programs. With SYS(1104) you can force a garbagge collection in the handle pool. And finally, there's the streaming output buffer. Visual FoxPro keeps a bitmap of every form in memory. When it prints something to a form, it updates this bitmap and performs a bitblt operation to display it. This streaming buffer can get quite large. At 1280x1024 with true color, it's almost 4 MB for a maximized form. "

Now the question: there is a way to effectively limit the total amount of memory used? As I could understand SYS(3050) won't do it.

Thanks,

Fernando