Thank you for your reply...

>>I have a 'launcher' application run my APP. This controlling EXE creates a cursor or two while loading. Since this EXE does not get control back from the APP, it never cleans up after itself (the TMP files). How can I force it to clean up these files?


>
>It depends on whether the TMP files being left behind are the result of creating the cursors or temporary files that FoxPro creates

They're created because of temporary cursors. I have already tried doing a CLOSE ALL, but that doesn't do it. It only cleans up AFTER the controlling EXE exits! This is a problem when I have abnormal termination, and since the called APP never returns control (I dont do that to ensure finickey FoxPro quits)

>
>I took the solution to this problem a step further. On startup, my application creates a batch file to delete left behind TMP files. If the user exits normally, the shutdown routine deletes it. However, if they exit by either re-booting or turning the machine off, the batch file is left behind. My installation routine inserts lines in the user's AUTOEXEC.BAT to look for the file, and if present execute it. If it's found, AUTOEXEC.BAT will delete it after execution.

A very clever solution. This is my biggest complaint about VFP. I hate the fact that every simple (or what should be simple) task has to become a big song and dance. I'm sure MS spent plenty of time on the DB engine of VFP, but I think they need to spend at least as much time if not more on the front end!