Hi Ragnar,

It's known that VFP has sometimes that problem on PC's with 1Gb memory or more and limiting the buffer size fixes it. You can try to limit the size of VFP buffers.

SYS(3050, 1, 512*1024*1024)
SYS(3050, 2, 512*1024*1024)

Also try to call SYS(1104) after command that process large tables. It clears memory cache and buffers.




Take a look at Not enough memory for file map (Error 1150) Thread #727612 Message #727619.

>In an application handling rather large remote views (up to five milion rows) in a Visual Foxpro .dbc, and rather a lot of local queries to local .dbf:s, I'm getting the error message "Not enough memory for file map (Error 1150)" on what seems to be on random. My initial thought was that the size for table buffers was insufficient. There doesn't seem to be a way to set this in the later versions of Visual Foxpro though (the application is made in Visual Foxpro 8). I've tried the SYS(3050, 1|2, nBytes), but the setting doesn't seem to bite.
>
>This lead me into believeing that the memory manager uses the same memory pool for local queries and table buffers, whereby the combination of me doing a large enough query and keeping a hefty table buffer provoces the error "Not enough memory for file map (Error 1150)".
>
>My question is if there is a way to get information on how much physical memory the Visual Foxpro memory manager has available at any given time of execution, and in that case how.