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: MSI Project - Creating a DSN
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
‎Sep 10, 2008
03:35 PM
MSI Project - Creating a DSN
I am working on a MSI project and I need to create a SQL Native Client DSN to connect to a SQL Server 2005 Express server. On the DSN, I need to specify a username and password for SQL Auth. Also I would like to have the end user to be able to bring up a list of SQL Express servers on the network, choose the one they want to connect to; it should be only one, but can be named anything.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 11, 2008
06:32 PM
You can create a DSN, and specify the target server name by having the Server property using the ODBC Resources view. However, "user" and "password" for your odbc connection must be the parameters of your application. So your application must pass "user" and "password" to odbc DSN for making the connection to databases server.
If you are OK to bring up a list of all versions of Microsoft SQL Servers, you can use the built-in SQLLogin dialog that will be automatically displayed when you add a connection in the SQL Scripts view. You will need to delete the controls you do not want to display, and delete the Next control event that will execute the ISSQLServerValidate action using the Dialogs view.
Hope that helps.
If you are OK to bring up a list of all versions of Microsoft SQL Servers, you can use the built-in SQLLogin dialog that will be automatically displayed when you add a connection in the SQL Scripts view. You will need to delete the controls you do not want to display, and delete the Next control event that will execute the ISSQLServerValidate action using the Dialogs view.
Hope that helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 19, 2008
09:59 PM
Hi,
I created an SQL Script connection in my application which asks the user for authentications. Either windows authentications or user name / password.
Then, I created a ODBC DSN, where I set it to take the Server name from the aforementioned connection.
However, I am not sure how to pass the "user" and "password" to odbc DSN, nor the type of authentication.
Can you please elaborate more on that.
PS: I am using InstallShield 12 professional
Thanks in advance,
C.S.
I created an SQL Script connection in my application which asks the user for authentications. Either windows authentications or user name / password.
Then, I created a ODBC DSN, where I set it to take the Server name from the aforementioned connection.
However, I am not sure how to pass the "user" and "password" to odbc DSN, nor the type of authentication.
Can you please elaborate more on that.
PS: I am using InstallShield 12 professional
Thanks in advance,
C.S.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 23, 2008
03:32 PM
The user name setting is stored as 'LastUser' and the authentication type is stored as 'Trusted_Connection' in the registry. So you will need to add the following properties for your DSN in the ODBC view:
Property: LastUser
Value: [IS_SQLSERVER_USERNAME]
Property: Trusted_Connection
Value: [MY_DSN_TRUSTED_CONNECTION]
You will also need to set the value of the MY_DSN_TRUSTED_CONNECTION property based on the value of the IS_SQLSERVER_AUTHENTICATION property after you click on the Next button on the SQLLogin dialog. The MY_DSN_TRUSTED_CONNECTION property needs to be set to 'Yes' for the Windows authentication, or an empty string if otherwise.
Note that DSNs do not store passwords.
Property: LastUser
Value: [IS_SQLSERVER_USERNAME]
Property: Trusted_Connection
Value: [MY_DSN_TRUSTED_CONNECTION]
You will also need to set the value of the MY_DSN_TRUSTED_CONNECTION property based on the value of the IS_SQLSERVER_AUTHENTICATION property after you click on the Next button on the SQLLogin dialog. The MY_DSN_TRUSTED_CONNECTION property needs to be set to 'Yes' for the Windows authentication, or an empty string if otherwise.
Note that DSNs do not store passwords.