I am not doing much in vfp any more, but VFPA becomes more tempting - most of the enhancements scratch areas bothering me ;-)

I wished for such option less from isolation angle, but more from tweaking performance - deciding on the physical disc in JBOD
setups can give significant speed benefits, esp. when using traditional HDs.

Technological progress has gobbled up some of the benefits withh SSD eliminating most of "head seek" time, but Chens option clearly is a better solution.

Even smarter would be a way to change temp path for any new item while keeping the list of currently open temp files on previously set paths via SET command. Had issued such a enhancement wish, MS reaction was along the lines of "interesting idea, makes technical sense, but we won't go for it - usual user does not face such problems..."

Hats off to Chen!

>Many of us have wished that the TMPFILES= setting in config.fpw was more flexible so that (for example) each spawned West Wind instance or other app with multiple instances on the same PC, would use its own tmp folder.
>
>Chen has just released new versions of VFPA and VFP Compiler with some new config.fpw options allowing per-instance control over tmpfiles= : I intend to start using the VFPPROCESSID that uses _VFP.processid to ensure every instance is using its own folder.
>
>

     -------------------------------------------------------------------------------------------------------------
>     | Environment Variables      | Description                                                                  |
>     -------------------------------------------------------------------------------------------------------------
>     | User Environment Variables | For example, TMPFILES=%TEMP%                                                 |
>     -------------------------------------------------------------------------------------------------------------
>     | VFPPROCESSID               | The GetCurrentProcessId() Windows API, returns a 8-character name.           |
>     |                            | For example, TMPFILES=%TEMP%\%VFPPROCESSID%                                  |
>     -------------------------------------------------------------------------------------------------------------
>     | VFPGUID                    | The CoCreateGuid() Windows API, returns a 38-character name.                 |
>     |                            | For example, TMPFILES=%TEMP%\%VFPGUID%                                       |
>     -------------------------------------------------------------------------------------------------------------
>     | VFPTIMESTAMP               | Visual FoxPro TIMESTAMP data, returns a 10-character name.                   |
>     |                            | For example, TMPFILES=%TEMP%\%VFPTIMESTAMP%                                  |
>     -------------------------------------------------------------------------------------------------------------
>     | VFPPROCNAME                | The SYS(2015) function, returns a unique 10-character procedure name.        |
>     |                            | For example, TMPFILES=%TEMP%\%VFPPROCNAME%                                   |
>     -------------------------------------------------------------------------------------------------------------