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

Just checked (to be sure) as you suggested, but vfp (as normally) cleans up its temps very well, and this one was gone after I closed app. If it didn't, I'd be in bad shape since many of these temps are > 1 MB...

I'm a little familiar with temp file bloat, though, and I've seen it occur from various apps on user machines when apps/Windows don't clean up properly, either before or after closing, so your point is worth looking at, I would agree...

For example, right now in my temp directory, there are a bunch of files dated 10/15/98, when apparently something fouled up and some app didn't clean up right :)