I have a config.fpw file setting MEMLIMIT = 50,0,0. The applications have been running this way for years. They run on a Windows 2000 server. But now we are having problems with the app hanging.
Does anyone know if the above MEMLIMIT really impacts memory?
MEMLIMIT realy impact the memory (on Fox 2.6, I do not know if on Fox 2.5 too)
When you have 2. and 3. parameters = 0, fox ignores it and allocate much much memory from windows (on my machine 0.5GB).
I think it is simple like no MEMLIMIT parameter.
From help of dos fox:
MEMLIMIT
You can include the MEMLIMIT statement in the CONFIG.FP file to control the amount of memory that FoxPro for Windows consumes. The more memory you make available to FoxPro, the faster it will perform queries, sort files, and build indexes. However, the more memory you provide to FoxPro, the less that is available for other Windows applications. The syntax for setting the MEMLIMIT is
MEMLIMIT = <% of available memory>, [<Minimum memory (K)>] [<Maximum memory (K)>]
You allocate memory by specifying the percentage of available memory that you want FoxPro to use. In addition, you have the option of specifying the minimum and/or maximum amount of memory in kilobytes that you want allocated to FoxPro.
For example, specifying MEMLIMIT = 80, 1024, 4096 allocates 80 percent of your system's available memory to FoxPro with a minimum allocation of 1024K and a maximum of 4096K.
The executables reside on the server. The users run them from terminal server. The apps are in FPW 2.6. Don't know if memlimit is the cause. Just don't understand 50,0,0 meaning.
Thanks
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.