>David,
>
>Check to see if SYS(3055) helps.
>

In addition, there are several other things to consider:

(1) Where are the TEMP files being written, and what drive holds the Windows swap file? If VFP is writing temp tables to the same drive that has a dynamically sized swap file, you might run into a situation where WIndows is unable to expand the swap file.

(2) Is Virtual memory enabled on the machine? The swap file is used for more than just extended memory support; if the swap file is disabled, lots of things like the clipboard and OLE interfaces may fail tofunction because of errors reported as not enough memory.

(3) Is the problem system run in a very high resolution, deep color depth mode, with lots of Desktop icons and open Windows with lots of controls. Are a horrendously large number of fonts installed. These are all tied to a special memory heap called the GDI - under Win9x, the GDI is limited to 64K of memory. Running out of GDI is often reported as not enough memory.

(4) Is VFP overallocating virtual memory to itself? You may find that placing limits on the buffer space that VFP is allowed to use, perhaps in the range of 1/3rd to 1/2 of the available physical RAM, will make VFP behave better.

>>My client runs a Commission Report and it crashes with a "Not Enough Memory" condition on an SQL statement that uses some pretty big files with pretty big indexes. It crashes on my PC too. However, why I delivered a defective feature to them is that I tested this feature from the command window and had to test it so often for so long that I plain forgot to test it from inside the app.