Creating ODBC in MSI

I need to distribute an ODBC that has username and password authentication. Anybody shed any light or wisdom on the best and easiest way to do this. I am trying to use WinInstall LE, if there is a better way any advice would be appreciated.


0 Comments   [ + ] Show comments

Answers (9)

Posted by: vibhor 7 years ago
White Belt
Capture all the registries changes made by the Source application. On a clean workstation create the odbc connection manually and than import the ODBC "HKLM\Software\Microsoft\ODBC" registry hive. Password never reflect in registries hive however it store there. There is small chance of some files getting captured, you should include any file if newly created or changed.

  • This thread is nearly 4 years old - please don't resurect old threads. - dunnpy 7 years ago
Posted by: cygan 13 years ago
Fifth Degree Brown Belt
there are lots of info on odbc if you do a search

on a clean workstation create the odbc settings
then go into the registry and import your settings into your msi
Posted by: Stanimosity 13 years ago
Senior Yellow Belt
i have done a bit of research and am having trouble with the password part of the connection....don't see where that gets saved in the registry (or anywhere for that matter). Was also curious if anybody had specifically built a connection from scratch inside of Wininstall LE.

Posted by: AngelD 13 years ago
Red Belt
If I recall correct; you need to enter the authentication information using the Registry table as the ODBC related tables do not support that "info".
Posted by: Harsha Gurugunti 13 years ago
Senior Yellow Belt

One of the easy methods to know where password get saved is, run (taking first snap shot of machine) a "picture taker" or "InstallRite" before entering the connection password and re-run (second snap shot) the same tool after entering password. It will give you the correct result. Import/add them in the your MSI.
Hope this helps you.
Posted by: mekaywe 13 years ago
Brown Belt
I believe Passwords will not be saved anywhere
Posted by: dunnpy 13 years ago
Red Belt
You could try this:

"Server"="<Server IP/Name>"
"Database"="<Default Database Name>"
"LastUser"="<userid you want>"
"UserName"="<userid you want>"
"Password"="<password you want>"

The username and password keys are not created by default - I've got someone doing some UAT/OAT on a package at the moment with the DSN settings populated as above.

Works fine in my Dev Lab - waiting to see how the user experience is.

Hope this helps,

Posted by: DazFrost 11 years ago
Yellow Belt
When you go back into ODBC settings, does the password field show as being populated as mine is still clear...?
Posted by: dunnpy 11 years ago
Red Belt

I think that opening up the ODBC GUI may not show you the password - check the registry keys noted above and test that the DSN makes a connection on a box with backend connectivity.

How's things? Long time no speak :)


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ