>>>Sorry, I was being too vague. I wanted to set the temp dir in my config.fpw and I have this:
>>>TMPFILES = GETENV("TEMP")
>>>but it doesn't work.
>>
>>Nope, it won't work. That's why I mentioned the post setup executable. Peresonally, my post setup, which writes the configuration file, uses the directory that the executable's placed in for the temp. Once the application is installed, however, it has to be done by modifying the config (if it's not built in).
>
>This *is* my post-setup executable. I use the VFP Setup Wizard to get the app where the user wants it and register the TreeView, then they run my post-setup executable from the CDROM, which is a form-in-a-exe-wrapper to ask them where they just installed the app so Registry values can get written, etc. However, this executable for some reason wants to write to the HD in the same directory as the .EXE, no matter what. My current working kludge is to have the user dbl-click on a .BAT that copies the contents of the \setup2 directory to %temp% and then run the .exe from there. Stupid and ugly but it works.
>
>I have InstallShield for VC++ from Visual Studio 6 but that's a whole mess unto itself (where's the tutorial?!).
>
>I'm open to all kinds of suggestions.....
>
>:)

Steve,

Which temp files are we talking about? The one's created by the post setup executable or the one's created by the application itself? If it's the former, I wouldn't be concerned about them since they'll be deleted when the program tereminates.

What I was suggesting was that somewhere in the post setup executable, it actually writes the entire CONFIG.FPW file. All you'll need to do there is to do the following assignment:

lctmpfiles = "TMPFILES=" + GETENV("TEMP")

and write the lctmpfiles variable to the file with something like

= FPUTS(lnhandle, lctmpfiles)

Or am I missing something here?