>Oh no... I'm talking about internal VFP temp files that are created in the system defined temp folder. We don't have any control over these filenames to my knowledge. VFP creates them in 8.3 format. With so few characters to work with, I imagine there's a chance that a file may get overwritten by another instance of VFP...?? That is, unless the VFP developers check to see if the file exists first. I'm still investigating this problem and know I may be chasing the wind here... just wondering if anyone knows of a way to increase the 8.3 temp filename to perhaps 20.3??

Add a directory name to it.

Here's how: Have a launcher, which will in the end launch your app. Before it does that, it will create a directory, and create a config.fpw file in it, with the tmpfiles= setting pointing to that directory. Then it will launch the app with -c switch pointing to this config.fpw file. And all the temp files this instance of the app will create will reside in this directory. Periodically, you can delete the directories where all the files are older than two days.