Bernard,

In XP and Win2K, so I assume NT, there are settings of sorts that give some "control" over RAM allocation.

Things like more to cache or more to program.

You might see some differences playing with those.

good luck


>Hi Ramil
>
>Yes I looked at SYS(3050)
>
>Actually the way I measured the memory was to add a text box to my main form to show the result of SYS(3050,1) and a command button. Clicking the command button allowed me to enter a value into an INPUTVBOX() and then I ran SYS(3050,1,VALUE FROM INPTUBOX()).
>
>This displayed approximately correct figures as mentioned in the help file. But these figures were nowhere near that reported by NT Taskmanager.
>
>For instance when I reduced the foreground memory to 1000k, SYS(3050,1) returned 786 but Taskman showed 4000k!
>
>When I minimizes the app it dropped to 1765k. On restoring it went to 2050.
>When I just clicked on a DROPDOWN LISTBOX, taskman reported a jump to 6000k.VFP reported no change!
>
>This is totally inconsistent with the results reported by SYS(3050) which still reported 768k.
>
>We have a large amount of Physical ram but also a number of users (30+)so that is the concern.
>
>
>
>>We are using NT TSE as well. The SYS(3050) really helped us dramatically improve the SQL calls. However, based on VFP help file, SYS(3050) is usefull if there is a large amount of physical RAM (1 GB+). This will actually limit VFP's usage of memory to the setting set by SYS(3050,1,nnnnn). Try setting it to 10MB/8MB.
>>
>>Using SYS(1104), not sure if this is VFP 7+ only, at certain key parts of the app like before or after running a long process.
>>
>>Lastly, if possible, put the EXE and Data on the same drive.
>>
>>HTH.