We have several implementations... works very well.

We use a launcher program and copy everything to a local area based on the user that is logged in. The launcher checks the master copy of the program that is stored in a directory and refreshes the local version whenever it is run. All users have an icon to the launcher on their desktop when they login.

Essentially;

C:\APPNAME\Master_Dir\app_launcher.exe
C:\APPNAME\Master_Dir\app_exe.exe
C:\APPNAME\Master_Dir\"other files and dirs"


C:\APPNAME\Run_Dir\[user_name]
Files and folders are copied from Master_Dir to Run_Dir\[user_name]

Then the launcher.exe executes the local exe Run_Dir\[user_name]\app_exe.exe and quits.

The launcher sets the temporary workspace and other settings in a config.fpw file as well and copies it local.

We also have some that have a shared server - and the Master_Dir is on another server - nothing really changes other than the drive or UNC path to the master files.


>Hi All,
>
>Can anyone share insights and ideas about running a VFP application on a single server and allowing multiple people to run it, each in their own space i.e. so it does not interfere with other running instances.
>
>Thanks