Hi Ronald,

>With the change for SagePro, that is no longer the case and all users are sharing the same dependency files and creating an issue.

Why not? The TEMP file is user specific. What would prevent creating a separate temp folder for every user that does not contain a dot? VFP, by default, uses the content of the TEMP environment variable. You could create a small batch file which specifies a different TEMP location and then runs SagePro.

> I was wondering if it would be possible for SagePro config to be addressing the temp file location.

You could try to pass a config file using the -C command line option. This works for all VFP applications unless the config file is embedded and external files are disabled. Alternatively, if SagePro is not protected with something like ReFox, you could create you own EXE with a Config.FPW of your liking and then call the SagePro executable with DO.