Robert;

Glad the problem was resolved.

I have seen this problem with different versions of NT.40 Server, etc. Limiting the amount of RAM available to VFP would always work. NT would fight VFP for RAM and VFP would loose. Many people have told me over the years that this is not a problem. Guess again! When your client is down it is a problem and you find the fix.

Tom


>Late reply I know but limiting the buffer size with sys(3050) worked.
>It seems strange to me though to limit the buffer size when there is plenty of ram.
>Why would that be??
>I told the developers your suggestion but they had to hear it from MS directly before they tried it.
>Just found out today that it worked.
>Thanks,
>
>>You can try to limit the size of VFP buffers

SYS(3050, 1, 64*1024*1024)
>>SYS(3050, 2, 64*1024*1024)

Also try to call SYS(1104) after command that process large tables. It clears memory cache and buffers.
>>
>>>Has anyone seen this? A client is getting this error running a VFP process on a machine that has 4 gig of memory. I don't know what is in the process. It is not my code and I don't have the source code. They just called me in to see if I have any ideas. Task Manager shows memory usage only up to around 500,000k when the error occurs, so there seems to be plenty of memory available.
>>>
>>>Any ideas on what may be the problem?