Hi Denis

For what its worth I recently went through this whole issue with several apps that we are developing. My conclusion in respect of memory usage is this:

If your app will run, during a normal session, numerous "similar" queries on large files then leave the VFP memory settings alone and let VFP cache as much of the file for successive queries as it can. This will, however, leave less memory for other apps the user might run at the same time.

If, however, each successive query has little relevance to previous queries made, even if from the same file, then I found that flushing the VFP memory cache after each query, rather than limiting the memory, had a greater impact on performance. In other words, dont force VFP to manage a large cache of stuff the app will probably not use during the remainder of the sesion. The VFP cache flush command is undocumented but is SYS(1104).

I found that deciding whether caching a lot of the data files would be beneficial during a normal session or not is the first question to ask when deciding whether to limit the VFP memory pool or not.

As Sergey says, my 2 cents worth!

Jos