>Hi Thomas,
>
>The rise of memory consumption only occurs when I populate the cursors. If I ommit the method that inserts records in the cursor the memory consumed will be about 1MB. But if the insert method is there, there memory consumed reaches to 100+ mb which stays in the page file (Virtual Memory) until the application is exited.
>
"Insert" using append/replace into table, flush often and close the table during insert 10 - 100 times after appropriate number of the SQL read recs have been worked upon. If that still doesn't keep memory down and push comes to shove, offload the "insertion" task to an external vfp.exe, whose process / memory space can be eliminated after work is finished, enabling your program to carry on. Sounds inefficient, but if that is the ONLY problem, I wouldn't hesitate to implement such a cripple <g>. The external exe has to start only once and work upon the tables instead of cursor's (so the effort I mentioned in my privious post can be used here <g>). From reading between the lines I gather that your cursors probably are touching your disk anyway, so you won't loose much perf. Some cleanup work, but should be trivial compared to fighting windows' memory hassles.

my 0.02 EUR

thomas