Software Deployment

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.

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

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.

Thanks

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".

Stanimosity

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.
Cheers,

I believe Passwords will not be saved anywhere

You could try this:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<MyConnectionName>]
"Driver"="C:\\WINDOWS\\system32\\SQLSRV32.dll"
"Description"="MyConnection"
"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,

Dunnpy

When you go back into ODBC settings, does the password field show as being populated as mine is still clear...?

Daz,

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 :)

Thanks,

Dunnpy