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: Dynamic ODBC resource DSN Naming
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
‎Nov 01, 2010
01:28 PM
Dynamic ODBC resource DSN Naming
I've researched this and it appears many have asked, no answers to this question. I want to use a property that I set during the UI (via dialog) to name my DSN. How can I accomplish this? :confused:
Thank you
Thank you
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 01, 2010
03:55 PM
I have been able to manually insert the DSN's (and their dynamically set name) via the registry keys but was hoping to see if there was a solution with using the DSN ODBC Resources option in System configuration.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 04, 2010
01:53 AM
The Description field of the ODBCDataSource table, which holds the DSN name, does not accept "formatted" text (which may contain properties), but only static text. This means that it is not possible to set dynamical DSN names via the InstallShield ODBC options.
You might use the registry instead (as you say you have done). I have written a custom action that uses SQL to modify ODBCDataSource.Description.
You might use the registry instead (as you say you have done). I have written a custom action that uses SQL to modify ODBCDataSource.Description.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 05, 2010
12:11 PM
Yea, I guess just altering the registry will work. Too bad the ODBC area doesn't have that flexibility.
I did find placing into registry manually is easy, I just create a new feature, add a registry component to that feature, and the key entries are so easy for DSN's (at least that is :))
I did find placing into registry manually is easy, I just create a new feature, add a registry component to that feature, and the key entries are so easy for DSN's (at least that is :))
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)