>>We have a spider process that runs some fairly intensive data processes in the background and have recently been receiving a number of inconsistent bugs.
>>
>>We believe we have narrowed the problem down to a resource problem. After running one data intensive process after another, VFP does not release the memory right away and eventually, we run out of resources. The results at this point are unpredicatable. Tables that were opened up one line before have been closed. Memory variables that we declared a few lines above suddenly have disappeared.
>>
>>We are going to issue a Sys(1104) after each process in hopes of getting some of the memory back. My experience has been that you don't get all of it back.
>>
>>We would also like to added to our error log the amount of RAM in use at the time of the error. FoxPro's Sys(1016) is not adequate for what we need.
>>
>>What are some API calls that would give us an accurate picture of memory in use?
>>
>>TIA
>

---

>
>look at API #12725
>
>But, eh, what does Sys(1104) do? I can't find it in my VS7 help file.

Thanks, I ended up using that code. But I have a question, my boss has said that binary storage depended upon the processor. Some store as LITTLE_ENDIAN, others store as BIG_ENDIAN. This function doesn't make a distinction based on different processors. I had always thought that all storage was LITTLE_ENDIAN.

I am not fully familiar with Sys(1104) but I will tell you what I know. FoxPro has a tendency when processing large files to keep some of the memory used to process those tables. I believe that Sys(1104) is supposed to retrieve that lost memory. My experience has been that it only retrieves a some of it.