Malcolm,
This is the only technique I employ and I applaude you for jumping in with this. I stopped using the Setup Wizard a long time ago. When faced with creating commercial application installations, the setup wizard left a lot to be desired. Because the installation packages I was using at the time did not support the post-setup executable (IS and later Wise), other methods needed to be used.

>PMFJI,
>
>One of the ways that we have handled the post-executable issue is to install a 'flag' file like MyApplication.1st in our application's startup folder. In MyApplication.exe's startup code, we check for the existance of a MyApplication.1st file - if its present, we know that this is the first time our application is being run ('sort of' equivalent to a post-installation event) and we run our post-installation logic (internal VFP code and/or one or more external executables) and then delete the MyApplication.1st flag file. Otherwise we procede with the standard application startup.
>
>The benefits to this approach are:
>
>1. If a user screws something after they've been using our application, we can have them create a MyApplication.1st file via Notepad and then have them restart our application, retriggering our post-installation logic.
>
>2. You can write your post-installation executables in VFP because you are (relatively) certain that the installation *transaction* has successfully completed, i.e. if certain files were in-use during the primary installation, then a reboot may be needed. Trying to run post-installation executables before this reboot took place might cause problems if there are dependencies between the files being replaced and the post-installation executables.
>
>Hope this helps!
>Malcolm
>
>
>>Claude,
>>While this is an innovative use of the dialog, it isn't quite the same. Have you ever installed a piece of software and a dialog asks if you want to run it after the installation is complete? That is the same dialog in question here. The end user would have the ability to opt out of running your Post-Setup executable. With the ability to actually setup an after installation program, the end user would have no way of declining it.
>>
>>>Sure!
>>>1.) go to Dialogs
>>>2.) Go to 'Setup Complete Success'
>>>3.) Say Yes to 'Show launch program'
>>>4.) Put in your .Exe in 'Program File' (the file needs to have been included in the setup already). As a simple test, include Notepad.exe
>>>5.) Put in any parameter in the 'Command Line Parameters'. As a simple test. put in any .txt file
>>>
>>>>>You can run a post-executable with the new included Installshield VFP limited. I did this on Sunday. In addition, it's an improvement that you can pass it a parameter...
>>>>
>>>>
>>>>Can you tell us how you did this?