Ed and Evan
Thanks for the help. I thought you would like to know how I got around the problem. As Evan said, you can create a setup program with almost nothing to install. I found that if the directory is empty the setup wizard will stop. I created a sub dir \wsinstl and only put an icon file in it. When I ran the wizard I set the PM checkbox and set the path and program name to my real exe. The user only needs to know the location of the real exe on the network. That is no problem.

John.


>>>What I usually do is take a single empty PRG file and then create an install routine with the setup wizard. Be sure to check 'include VFP runtime' (or some such wording). I have seen other say that you don't even need to have a dummy PRG with with SP3. You can then distrubute the setup files to your users on a netork drive, via a floppy, etc..
>>
>>Evan,
>> Thanks. It seems to work. Is there any way to install a shortcut on the users pc to the existing exe on the network?
>
>Only if you know where it is; the WSH Wscript.Shell object has a facility for creating shortcuts in it, so a post-setup executable that can find the network .EXE and build the local shortcut would address the problem nicely.