>>I didn't catch the first part of this thread, but one thing that can lead to memory usage is the use of cursors. Whenever you do a lot of select statements into cursors, the temp directory can get pretty full (the bigger the cursor, the fuller the temp directory). Two solutions might be 1]After you use the cursor and know that you won't need it any longer, you can issue a "USE IN ALIAS('Cursor')" and this I think will release the cursor from memory or 2]write a custom class that monitors what actual names are being assigned to your cursors down in the temp directory of the local machine and in the destroy event of your form, it deletes that file from the temp directory.
>>Hope this is applicable to the original thread.
>
>I don't know, I've found the opposite to be true...an app was slowing to a crawl until I implemented SQL into cursors, many runs will do this 50,000 or more times, and the cursors are quite large. As long as I use the same cursor name every time, it appears to overwrite and cleanup the previous one very well automatically...also, USE IN doesn't seem to make any difference...

I think what was meant was not re-creating cursors (ie. overwriting) but creating different cursors and not closing them. Which would obviously use real or virtual memory...

Joe