SQL Query Tab

Schedule Action to Run SQL Query

The SQL query can be triggered by scheduling the associated custom action in the install execution stage or by directly invoking the custom action with a published event.

Abort installation in case of error

Abort the installation if an error is encountered during query execution.

You can suppress the spawned message box for the SQL query operation by setting the SqlSuppressSpawnMsgBox property to 1. You can set this property statically (from Install Parameters) or dynamically (from the installer UI - associated with an Edit Control or with a Set installer property value Initialization/Published Event).

Adding a new data binding

Use the [ New... ] button, the “New...” context menu item or press the Insert key while the list control is focused.

Moving a data binding

Use the [ Up ], [ Down ] buttons, the “Up”, “Down” context menu items or press the Page Up, Page Down keys while the list control is focused.

The top-bottom order of the data bindings is important because it will represent the left-right columns order in the result set.

Removing a data binding

Use the [ Remove ] button, the “Remove” context menu item or press the Delete key while an element from the list control is focused.

Results

The specified binding properties will be used by Advanced Installer to return the result set values:

• any ComboBox control that has the above specified properties associated with it.
• any ListBox control that has the above specified properties associated with it.
• the first row from the result set will be bound directly to the above specified properties.

For an example on how data bindings are set in an SQL query follow SQL Query Examples.

Script File

Specify the file for the query. Use [ ... ] button to select it.

Script Inline

Use the embedded editor to instantly create a query on the fly.

Statement separator (SQL Batch file separator)

Specify the separator for the SQL statements.

By default this field is empty; if you supply a statement separator (Eg. semicolon ; or GO ), during installation the SQL script batch file will be automatically split into component statements using the supplied statement separator and each SQL statement will be executed individually. Otherwise, SQL script will be executed as a whole. Format: with the exception of semicolon ; , the statement separator must always begin with a letter and can contain only alpha-numeric characters.

Some Database Servers do not permit executing multiple statements at once. In this case supply a statement separator to indicate that the SQL queries should be executed individually. For more information please read Why does my SQL Script fail to run when executed from the installer? FAQ.

Strip comments from SQL script

Removes all comments from the SQL script. (This option also removes SQL comments from your stored procedures, if any.)