Karen, First see if a disconnect will release memory. You can watch this with task manager.
My experience has been that the only way to get memory back that has leaked is to close RBase. Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, August 10, 2012 2:59 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Cursor ideas? Alastair: we tried putting a disconnect and reconnect at the beginning of running the program and that didn't help. I suppose I could change it to use a permanent table rather than temp, running maybe 15K rows of the cursor, jump out of the cursor, do a disconnect and reconnect and then jump back into the cursor using a flag column to keep track of what I've done and what I haven't yet. Haven't tried that. That might be a quicker test than converting to a GoTo. Keep the good ideas coming! Karen In a message dated 8/10/2012 12:35:33 PM Central Daylight Time, [email protected]<mailto:[email protected]> writes: On the other hand, if you have to go this route, you might find that just disconnecting and reconnecting will do the trick – if so it’s easy to automate... Regards, Alastair.
