>Andrus,
>This is from VFP online doc as is :
>For the most part, the Windows NT® operating system and Visual FoxPro work extremely well together. The only exception is when you run Visual FoxPro on a Windows NT Server. The Windows NT Server uses far more memory than Visual FoxPro expects, and therefore Visual FoxPro can tend to over-allocate memory for its own uses.
>To remedy this, you should use the SYS (3050) system function to adjust Visual FoxPro’s memory buffer pool to approximately one third of its default (see the Memory Management section below). For example, you could add the following code to your startup code or your CONFIG.FPW file:
>
>=SYS (3050, VAL (SYS (3050, 1, 0)) / 3)
>Cetin

This may or may not always be valid. Malcolm Rubel had an EXCELLENT session at VFP DevCon concerning VFP performance. His benchmarking seems to refute Microsoft's claim as quoted by Cetin above. Malcolm's benchmarks definitely show definite differences depending upon what database operations are being performed, how much memory is on the machine, etc. His general recommendation was to leave SYS(3050) alone unless you want to tweak it by doing your own benchmarking using your own code and data.

I tend to agree with his conclusions.