>>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.
>
>if u can, do it please... because the only thing that i found is the Win95 Memory Configuration at Performance/System
>
>well... i stay here waiting...
>
>thanks

Ariel:

It's in a very interesting article in FoxTalk Frebruary 97. In Essence:
Play around with SYS(3050,1,x) where x is the amount of "real" RAM as opposed to RAM+SwapFile that Windows returns. In teh article the authors found that for their 32 MB system (with only VFP loaded) the ideal setting was SYS(3050,1,15500000) and for their 16 MB system (ditto) SYS(3050,1,7400000). There's one thing that bothers me though: VFP 3.0 *did not* have its own memory manager (that's why MEMLIMIT was ignored) so it could be something else...