Thanks for the reply Wayne. I'm familiar with the TARGETDIR variable in InstallShield but have never had occasion to use it. You can create custom folders in VSI, I did this to create an entry on the Start|Programs menu. I haven't tried to move the app from the Program Files directory but I don't know why you can't just drag the exe from that folder to any other.
BTW, congratulations on your MCP in SQL7 Admin., that's a tough one. I've gone through both 6.5 and 7.0 admin training, and have a couple of years experience, but I'm too chicken to try! Everyone I've talked to here in San Antonio that has taken it has failed.
>I worked with it for a few hours, and was impressed... the only thing I found that I could not get to work is the ability to store the target installation directory (Local and Network) in the registry. In Installshield, you can have the variable (TARGETDIR?) evaluated and stored in the registry based on the user's choice.
> Our application setup will always be installed from a shared network directory - we just can't guarantee what the name will be. Nor can we guarantee where they will install locally. The reason we need this information is that any updates we send out are copied to their network drive first then each workstation updates itself if necessary.
> You also seem to be forced to install your application in the 'program files' directory. I know this is the Windows thing to do, but not all applications are designed this way.
>
>
>Wayne
Bob Tracy
Never engage in a battle of wits if you're only half armed.