Thank you David! The issue I'm having is that our main installer in the distribution is currently an .msi itself with no wrapper .exe, so we would need to create a wrapper in order to launch the additional .msi. We have an .exe Setup wrapper, but it's just an information splash screen that directs the user to choose the appropriate .msi to launch depending on their choice (multiple product modules can be chosen and installed separately). We are leaning toward shifting the burden to the end-customer for running the .msi as a prereq, but distributing the .msi with the general package anyway. We may try to add it as another "choice" on the Setup.exe splashscreen, but the ideal way would be to be able to add the install .dll for the driver as a custom action in our installer script. If this is not possible (i.e., if there simply is no installer .dll for ODBC 17.6.1), we'll just have to work around it. 🙂
Thanks again.