>hi guys,
>
>I found these in the knowledge base. They are for VFP 3, but seem to discuss some of this stuff in more detail. I don't know how much has changed from 3 to 5 & 6.
>
>They supprt some of the comments made in this thread. They point out for example that MEMLIMIT is no longer relevant. They also discusses virtual memory as a size limit, and that VFP grabs blocks of memory as needed, and only returns extra space if the OS asks for it. I don't know if this clears things up or not.
>
>I personally, would be interested in finding more about this. I like to know how things work, and its interesting too as memory management seems to have evolved with VFP--I guess I am a history buff too. *s*
>
>http://support.microsoft.com/support/kb/articles/Q136/6/94.asp
>http://support.microsoft.com/support/kb/articles/Q130/5/22.asp
>
>HTH
>Bill

Bill,

We were having a problem with memory and a VFP app (VFP6). After calling Microsoft Tech Support, they suggested we use the MEMLIMIT command. The TS person said that MEMLIMIT was no longer documented on what it does to VFP memory, but it DOES still have some effect, though they would not provide me any details in what it does do. BTW, it didn't fix our problem, but it sure was able to make it move around! (Failure to Instanciate Object, followed by Insufficient Memory errors) So it really does appear to have SOME effect, but I don't know what.