Here's one way you can do this:

1) Copy (do not install) your EXE and the necessary DBC's and DBF's to the desired directory or directories on the file server.

2) On your development machine, create a distribution setup for the VFP runtime files. You can do this by creating a project with nothing but a MAIN.PRG, which in turn does nothing but RETURN. A "netsetup" type of distribution works well for this purpose since it creates a single set of files in a single distribution directory.

3) Copy the netsetup distribution files from step 2 to the file server, into a directory of their own. A subdirectory of your app called "setup" would work fine, or you can put them in any directory that all workstations can access.

4) On each workstation, use the "Run" window to run the setup.exe you copied to the file server in step 3. This installs the VFP runtime files on the workstation.

5) On each workstation, create the desired desktop shortcut and/or program start menu entries to point to your EXE on the server.

That's about it. If your app uses any ActiveX controls that are not already present and registered on the workstation, you'll need to install these too.

Performance will be improved if you direct VFP's temporary files to the local workstation's hard drive rather than to the file server. You can do this by including a CONFIG.FPW in your project that specifies where TMPFILES should go, for example TMPFILES=C:\WINDOWS\TEMP.

---

>Hi,
> I need to distribute a multiuser application which will share a database in server.
>
>

>Terminal          Server   Workstation1   Workstation2   Workstation3
>Database          YES      NO             NO             NO
>Application       YES      NO             NO             NO
>
>

>
>According to the database and application allocation above, how should I distribute my setup program? Should I include DB in every setup disk for them? Or how the distribution disk being developed for this situation?
>
>Thank you