The next time you're running one of your apps, minimize FoxPro and go into the system temp directory and look for the most recently created temp file. After noting the name of this temp file and making sure that it's time stamp matches the time you are running your app, go back to FoxPro and close out the app. Then go see if the temp file is still there. Even if you're using the same cursor name over and over again in your app, I think you're still leaving the cursor down there loafing around in the temp directory, and this hogs up a lot of unnecessary space on the user's machine.
It's probably not a big deal in most situations, but something to think about! If "USE IN ALIAS" doesn't work, it shouldn't be that hard to write a custom class that handles deleting temporary files. Let me know what you think.


>>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...