>>>>>Indeed, there is something you can do. There problems lies in the fact that VFP3.0 had it's own memory manager while VFP5.0 uses the win95 memory manager (it has to in order to be win95 compliant). Basically, the win95 memory manager doesn't give VFP5.0 the memory it needs because it includes virtual memory in what it allocates. So, a lot of memory swapping to the hard drive occurs.
>>>>>
>>>>>In order to alleviate this problem you need to specify the memory VFP uses manually. Darned if I can remember the command to do so and I don't have my notes right here, but if you can't find the command drop me a line and I'll look it up for you.
>>>>>
>>>>>Michael G. Emmons
>>>>>VFP Programmer Extroidinaire
>>>>>
>>>>>
>>>>You mean Memlimit? I didn't think that worked any longer...but if you know another manual memory command, I'm interested too.
>>>>
>>>>Another way around the swapping problem is to set your Win95 virtual memory to around 20 meg or less, this forces use of RAM...
>>>
>>>check sys(3050). also a thread or two a while back on this...
>>
>>Hmmm...I tried some various settings, but sys(3050) doesn't seem to distinguish between virtual & RAM. It allows me to set memory higher than my RAM without any message...does that sound right? If so, how can we be sure that it will always use RAM?
>
>if i remember the thread correctly, it can't distinguish between ram and virtual memory (95 treats it all the same). goal was to lower amount to use little virtual memory so vfp wouldn't churn to the disk thinking it had the real thing. i think paul maskens and tom o'hare were the chief contributors to this thread. also a recent write up on this in foxtalk (april issue, i believe)

search here on '3050' or title VFP 3.0/5.0 Memory and performance.