No, it only takes once for the climb to start from 89000K to 138000K in one pass.

Yes Close All has been tried. Did not release memory back. I can do this from the command window with the same results. No hanging anything(s) out there.

I'm running on a 233 with 128 meg of ram. NT 4.0 server sp 4. Can duplicate problem on NT workstation same level.

The cursor is around 250000 records 5 field. CAN'T SOMEBODY HERE ME.

I really don't want to call MS and stay on the phone the rest of my life.


Jeff

>Jeff,
>
>I presume that you execute this several times and that RAM decreases with each execution. Is that correct?
>
>And you have tried a "CLOSE ALL" between each of those executions, without success (not a "USE" on each, as you show here, but an actual "COLSE ALL".
>
>Those being accurate, I am at a loss. But surely someone here will come u with the answer.
>
>good luck yet again,
>
>Jim N
>
>>Here is what I do
>>
>>STORE SQLCONNECT('&as4sys','','') TO gnconnhandle
>>
>>STORE "SELECT * from mydbf" TO sql1
>>
>>ckq=sqlexec(gnconnhandle,sql1,"tempcursor")
>>
>>*Memory starts going away here until all records returned*
>>
>>USE DBF('tempcursor') IN 0 AGAIN ALIAS stuff SHARED
>>
>>select tempcursor
>>
>>use
>>
>>=SQLDISCONNECT(gnconnhandle)
>>
>>select stuff
>>
>>use
>>
>>* Memory still inuse*
>>
>>Just standard stuff, but I can't get it back. The file large, several meg, but it returns in less than 2 min. (Good for this app). Testing indicates this happens with remote or local data. I've got to missing something......
>>
>>Jeff
>>
>>>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