While I have not used InstallShield, the situation with the VFP6 Setup Wizard may be similar.

I created "setup disks" for the workstation. This allowed me to indicate the run-time support, support for help files, and some required ActiveX controls.

Since the Setup Wizard insisted on specifying an executable (this part may be different in InstallShield), I made a copy of a small program (I used calc.exe, the calculator).

After installing the program on the user's machine, I deleted the dummy executable (actually, its entire folder, which I didn't need) manually. With the Setup Wizard, this part might be automated with a post-setup executable. This was not worth-while for me, since I only needed to install the run-time support, etc., on 10-15 machines.

For creating the icons, take a look at download #9419, by George Tasker. Presummably, in your case this would also be invoked from a post-setup executable.

HTH,

Hilmar.

>I recently upgraded to VFP 8.0 and am now faced with trying to build and installation program for an application that I am about to market. I have several scenarios that I want to build for:
>1. Single-User - Stand Alone PC
>2. Multi-User - Network Installation
> - Workstation Installation
>
>I realize that the Single-User and Multi-User(Network) installations would be the same, but how can I create a setup program that will just load the VFP runtime modules and create an icon on the users desktop?
>
>Any help or suggestions would be appreciated.
>
>Thanks!
>
>Dave :-)