Why does my SQL Script fail to run when executed from the installer?
When using PostgreSQL or MySql, if the script contains several statement separators it may execute without error outside the installer when run from a dedicated SQL editor.
This usually happens because some SQL dedicated editors can automatically parse different statement separators within the same script. As Advanced Installer does not support this, a solution is to define only one statement separator type for each SQL Script you add in the SQL Script Page. The Statement Separator can be defined from the script's settings on the right pane.
For example, here's what you can do if you have a script that includes several small ones delimited with different statement separators:
- split the script into separate .SQL files so each has only one separator type
- add each script in the SQL Scripts Page in the order you need them executed (top -> bottom)
Why doesn't the port number field get validated in the SqlConnectionDlg?
This behavior is caused when connecting via SQL Server ODBC resource by an incorrect SqlConnectionString format.
The following new syntax for the Server keyword was recently introduced by Microsoft:
Server=Server[,port]
For example:
Driver=[\{]SQL Server[\}];Server=[SERVER_PROP];Port=[PORT_PROP];Uid=[USERNAME_PROP];Pwd=[PASSWORD_PROP];Database=[DB_PROP];will become:
Driver=[\{]SQL Server[\}];Server=[SERVER_PROP],[PORT_PROP];Uid=[USERNAME_PROP];Pwd=[PASSWORD_PROP];Database=[DB_PROP];