Hello Jon,
After further investigation it seems this is caused by an Advanced Installer limitation, thank you for bringing this to our attention. In the former versions of Advanced Installer we have used the
"InstallODBC" Windows Installer standard action to install DSNs.
Starting with the newer version of Advanced Installer, in order to avoid some drawbacks of the above standard action, we have implemented a proprietary ODBC custom action (i.e. AI_OdbcInstall) which is used to install ODBC drivers and DSNs. However, it seems the related behavior (database field is blank) is caused by a limitation of our new "AI_OdbcInstall" custom action. A fix will be added in a future version of Advanced Installer. Until then, as a workaround, in order to avoid this issue you can proceed like this:
- go to "Custom Actions" page and add a "Set installer property" custom action with sequence, scheduled after "Wizard Dialogs Stage -> Searches" and "Install Execution Stage -> Searches" actions group, like this:
- Property: AI_USE_STD_ODBC_MGR
Value: 1
- build and run your project
When the "AI_USE_STD_ODBC_MGR" property is set the setup package will use the "InstallODBC" Windows Installer standard action to install DSNs instead of our new "AI_OdbcInstall" custom action.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging