>Hey Ed:
>
>I found this post of yours an wanted to ask you how you handled running the VFP6 Setup.exe and its dialogs? I too use Installshield Pro and have been for some time now. I've once used LaunchApp or LaunchAppAndWait to fire sub-installations, but if you're calling Visual Foxpro's Setup.exe, did your users have to walk through VFP's installation interface? You said you fired it "silently" from within the IS script and am curious about how silent it was?
>
>I'm in the process of moving a VFP 5.0 application to VFP 6.0 and remember the difficulty we had with runtime requirements for 5.0. I rather dread 6.0's.
>

How silently depends on which of the /Q options you choose to use when running the install. Build a NetSetup with the runtime in it. Once it's built, go to a DOS prompt, change to the directory your NetSetup is in, and enter the command SETUP /HELP. It'll pop a messagebox with all the command line switches of possible interest.

If you search my past entries on installation, I've posted the list of command line switches available to you, and some suggestions on things to do in terms of determining if reinstall is needed, and creating a parsable log, as well as silent running.

>Thanks for the tip.
>
>
>>I still generate a Setup Wizard install to put the runtime in place - I fire it silently from within my IS script, and this relieves me of responsibility for figuring out the runtime requirements - if a new Setup Wizard distribution is released (like VFP5 - VFP6, or VFP6 to VFP6 SP3) I can simply replace the previous runtime install with the new one and not worry about it.