This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Is_sqlserver_password
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 09, 2009
01:54 AM
Is_sqlserver_password
I have situation where I need to get the password that user inputs during the SQL Login, to create a DSN for MySQL Connector with that same password.
I tried to keep the DSN attribute
PWD [IS_SQLSERVER_PASSWORD]
But after the installation I get a blank password.
Just to make things clear,
I start the installation get a dialog (SQLLogin) where I input servername, username and password.
I want the inputted password for configuring my MySQL ODBC connector. So I assign the attribute PWD with [IS_SQLSERVER_PASSWORD] but it turns up as blank.
I tried to keep the DSN attribute
PWD [IS_SQLSERVER_PASSWORD]
But after the installation I get a blank password.
Just to make things clear,
I start the installation get a dialog (SQLLogin) where I input servername, username and password.
I want the inputted password for configuring my MySQL ODBC connector. So I assign the attribute PWD with [IS_SQLSERVER_PASSWORD] but it turns up as blank.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 09, 2009
02:31 PM
I don't think that DSNs save passwords for security reasons. If you configure a DSN through the Control Panel, the password field will be blank the next time you open the configuration panel.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 10, 2009
09:52 AM
Storing password seems to be vendor-dependent. I was checking with a DSN for Microsoft's SQL Native Client ODBC driver which doesn't store the SQL login password.
In order to investigate your issue, could you generate a Windows Installer verbose log for the installation, and see how the IS_SQLSERVER_PASSWORD property gets set? Also, please check if the PWD entry is created for your DSN in the registry.
In order to investigate your issue, could you generate a Windows Installer verbose log for the installation, and see how the IS_SQLSERVER_PASSWORD property gets set? Also, please check if the PWD entry is created for your DSN in the registry.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 11, 2009
01:11 AM
I wrote an install script to write the property IS_SQLSERVER_PASSWORD and it does write it. So the property does get stored.
It maybe a sequence problem, I think I should execute the ODBC connection only at the end, but I am not sure how I would do that...:confused:
EDIT:
Yippeeee, I got it working by changing the InstallODBC sequence and putting it in the last.
Thanks for helping me think 😉
It maybe a sequence problem, I think I should execute the ODBC connection only at the end, but I am not sure how I would do that...:confused:
EDIT:
Yippeeee, I got it working by changing the InstallODBC sequence and putting it in the last.
Thanks for helping me think 😉
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)