Jeff,

Then my last guess would be the infamous "dangling object" - you know, the thing where you tell VFP to RELEASE the object, it goes ahead and removes it from the MEMVAR list BUT actually keeps the object RAM occupied.

Is there any chance at all that you have such a "dangling object" reference??

Good luck (again),

Jim N

>Well Thanks anyway, but that does not help our situation. Close all, clear all release all, NOTHING RETURNS THE MEMORY. I could live with the memory if it peaked and then just never let that go, but the next time I run the prg, it builds from where it stop the last Time. I've got 128 meg of memory, but two times thur and I'm all out. I can't beleive no one else has seen this.
>
>Jeff
>>Hi Jeff,
>>
>>Don't really know if yours is the same situation as our 'anonymous bureaucrat' had, but it sounds like it could be similar, and he reported success issuing a CLOSE ALL periodically.
>>
>>Good Luck,
>>
>>Jim N
>>
>>>I'm sure I've seem this but I can't seem to find any related threads. I got a prg, no com's, no objects, just code. Gets data from an AS400 into cursors. Everything works well but memory use climbs with each run and I can't get fox to turn it loose. I have to quit FOxpro in order to recover. Ran program in both 5 and 6, same results. Is there a work around or is it just me?
>>>
>>>TIA
>>>Jeff