PMFJI, but Citrix NORMALLY creates a private temp directory for each user, by default under the standard NT TEMP directory. Each user gets a directory with their Citrix session ID as the name, to which only they have permissions. This can be disabled by running the FLATTEMP command, which is NOT normally recommended. Most programs respect this temp directory redirection, but there are a few that do not. I believe it has something to do with which API call is used to retrieve the temp directory location. A problem can arise with this scheme if the system is shut down while users are still logged in. On each reboot, Citrix session IDs start incrementing from 0 again (0 is always the console), and if a directory under temp already exists, it is not recreated and the permissions are not changed, resulting in a user with a temp directory to which they do not have permission, which, depending on the application, cna result in all sorts of strange errors, many of which do not make it obvious what the problem is.
Another option on a Citrix server is the HOMEDRIVE mapping. This will set a drive letter of your choosing (W: is commonly used) to a private directory (actually the user's profile directory). This will give you a common base path for an app such as VFP that needs private working directories. For example, if you set HOMEDRIVE to W:, you can set VFP's temp directory to W:\TEMP and be confident that it will be a unique directory for each user.

Randy


>Hi!
>
>I do not recommend you to do this. When all temporary files are in the same >folder, you can easy get a collision in temporary file names. Win 2000 has >different temporary folder for each user account located in the user profile >folder. Citrix do not have this that ccan cause conflicts. Better handle this >in application. When you have an EXE, current path really make no difference, >unless you use it to access data.