>>How is this done?
>>
>>>
>>>The CONFIG.FPW is usually compiled into the executable and, therefore, cannot be tampered with after distribution.
>
>Simply include an appropriate CONFIG.FPW under either Other/Other FilesOther/Text Files in your project when you compile the .EXE, and it's bound into the executable. My objection to doing this is that I can't change where the temp files reside easily without moving the location of the .EXE file and not setting the location in CONFIG.FPW or the equivalent.

Do you see it as a problem that if you don't bind the file to the EXE, anyone with Notepad and access to the CONFIG.FPW file can add lines?

I would bet that there are applications out there that if someone created a CONFIG.FPW file with the lone line SCREEN=OFF, people would have problems.

Imagine this disaster recovery plan:

Step 1: Overwrite EXE. Doesn't work. Still don't see anything.
Step 2: Recover from last known working backup. Doesn't work (didn't have an old CONFIG.FPW so it wasn't overwritten).
Step 3: Go out of business.

Joe