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
- :
- ODBC Resource Key File
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
‎May 13, 2011
10:10 AM
ODBC Resource Key File
I have an installation that has been configured to include/create two ODBC connection. This creates them correctly.
The problem I have is that if an end user modifies or deletes the ODBC connection then the MSI auto repair starts to fix them. I need to disable this, but I cannot find how to do this.
Any ideas?
The problem I have is that if an end user modifies or deletes the ODBC connection then the MSI auto repair starts to fix them. I need to disable this, but I cannot find how to do this.
Any ideas?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 16, 2011
02:58 AM
If it helps, I am using a Basic MSI project.
Inside the component that is created there are no files or registry settings, I cannot see what I can do to stop the ODBC connection being auto-repaired other than maybe a VBscript (or similar) being used to create the connection.
Inside the component that is created there are no files or registry settings, I cannot see what I can do to stop the ODBC connection being auto-repaired other than maybe a VBscript (or similar) being used to create the connection.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 16, 2011
03:38 AM
The ODBC entries are entry points into the MSI as they are created via the ODBC table.
If you remove the ODBC table entries and add the registry keys for the ODBC settings directly into a components registry instead then the problem will be removed.
Remember if you set a keypath to one of the registry keys which will get deleted when a user removes the odbc entry then it will still self repair.
If you remove the ODBC table entries and add the registry keys for the ODBC settings directly into a components registry instead then the problem will be removed.
Remember if you set a keypath to one of the registry keys which will get deleted when a user removes the odbc entry then it will still self repair.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 16, 2011
03:43 AM
Inabus wrote:
The ODBC entries are entry points into the MSI as they are created via the ODBC table.
If you remove the ODBC table entries and add the registry keys for the ODBC settings directly into a components registry instead then the problem will be removed.
Remember if you set a keypath to one of the registry keys which will get deleted when a user removes the odbc entry then it will still self repair.
Thank you Inabus, I have just seen this thread which has given me the same idea.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)