I have not yet upgraded to IS 2016 (still on 2015 SP1) but am posting here to be more current. We currently have 3 choices for ‘Script Error Handling’ when running SQL scripts: o On Error, Goto Next Script o On Error, Goto Next Statement o On Error, Abort Installation
The difficulty is that only the last one posts an error message. I understand that you may not want an error message for unattended installs. But for attended installs it would be nice to know that the script failed but still be able to complete the installation. Could you implement something like below where “Display Error Message” is a separate radio button? Default is to leave it unchecked for first 2 existing choices and checked for last existing choice. This would match current behavior. We could check it if we want to see error messages for the first 2 existing choices.
o Display Error Message
o On Error, Goto Next Script o On Error, Goto Next Statement o On Error, Abort Installation
Thank you for your input. The reason why InstallShield displays a SQL scripting error only for the "On Error, Abort Installation" option is that it would be annoying to dismiss the error dialogs when there are hundreds of SQL scripting errors. The SQL scripting errors are written to a Windows Installer verbose log if you are using a Basic MSI or InstallScript MSI project. Doesn't that help?
Thanks for the reply Hidenori. That makes sense. Unfortunately most users won't be logging the install. Logging the install is something I can do during development to be sure scripts are ok. I suppose the ideal situation would be if we had the ability to display that the script had an error(s) and not display all of them.
We can add the ability to store SQL scripting errors into a built-in property so that you can utilize the information for your requirements. Would that be helpful?
