Joe,

Why don't you want the .exe installed on the local workstation? You'll get (slightly?) better performance, and it would be easier to distribute updates...if you employ a launcher (see Nick's in downloads) an update can be deployed without kicking users out of the application. And without any additional action by each user, other than exiting the app and going back in.

>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
>
>