I'll try to explain better. I give someone a CD with my app on it. They are going to install it on a network so that multiple users can use it. They run setup.exe and install the application exe and dbf tables to
c:\program files\apps\appx. They share the directory c:\program files\ and now need to get other users computers set up. The user maps a drive "o:" to \\server\share. They need a way to install the runtimes,ocxs, and shortcuts. They don't want to run the same setup they just ran to do the network install. This would reinstall the exe and tables. So I assume I would make a new setup.exe for this. Named workstationsetup.exe, it would run and copy the runtimes, copy and register ocx's and create a shortcut that points to a drive mapped as o:. Installshield needs to create a folder on the LOCAL workstation off of "program files" called appx. In it they need a shortcut pointing to o:\apps\appx.exe. When the user is running workstationsetup.exe how can they create \program files\appx\appxshortcut and set the target of the shortcut to o:\apps\appx.exe


>Hi Joe,
>
>I can read what you wrote a couple of ways, but I'll assume you are creating an install .exe and you want to put that on the server so that workstations have access to it so they can run their setup. You said the first part was pretty easy so I assume you have the setup.exe on the server. With that, have the users use the UNC to find and execute the setup.exe. This way it won't matter which drive the workstation has mapped to the server. Provided the user has administrator privileges to the workstation they can run the setup.exe. The easiest way is to have them click start-run and then they can either manually type in the UNC or have them copy and paste it and then click OK. For example:
>
>\\networkserver\folder\VFPInstall\setup.exe
>
>HTH
>
>
>>I've just started looking at ISE. I figured I would need two installation
>>setups. One to load the exe and db on the server and a second to install the shortcuts/ocx's/runtimes on the workstation. The first part is pretty easy. However I'm not sure I understand how to allow the user to find the exe on the
>>server when doing a workstation install. Someone may have installed the exe in t:\apps\myapp or e:\program files\myapp on the server.