>Hi all,
>Is there anything left for me to do to prevent the "Not enough memory" error? Server is single core Xeon with 3GB RAM running Windows 2003 server. These are the settings:
>
>1. Server virtual memory is set to 4GB
>2. VFP tempwork folder is on a local D:\TEMPWORK
>3. SYS(1104) is sprinkled in the code.
>4. SYS(3050) has been set to 16, 64, 128, 256 and 512 but all these settings still gives the error.
>
>I would like to physically throw the vfp runtime dlls and exe across the room but that's not an option that's available to me. What else can I do?

Set vfp Memory to 64 ~ 192 MB to test for this.
Verify that the vfp memory space does not become too fragmented to load Rushmore bitmaps:
There is a vfp memory snapshot utility on Calvin's site but the same API is in one of the systernal tools -
don't remember where, but when I ran into something similar the results of both tools were the same,
with me banging my head on the kb because I had wrapped Calvin's tool and sprinkled calls to it into the app...

Also make sure there is enough room in the temp directory (cursors..., temp SQL index files ...). D:\Tempwork sounds good, but you never know...

And there is an error state vfp sometimes reaches where vfp cannot load printer drivers and/or fll's:
the same fll which could be loaded at start creates an error later on. Happens to me sporadically,
can identify it and work sometimes around it modifying sys(3050), but no pattern emerges. Verify if ***your*** error occurs that you can load a known usually working fll.

Kapersky AV is rumored to be bad for dbf - try the free MS offering.

HTH

thomas