/build/static/layout/Breadcrumb_cap_w.png

User DSN

Is there a way to capture or create a user DSN to be created on all users other than just the user installing the package?

0 Comments   [ + ] Show comments

Answers (8)

Posted by: kkaminsk 15 years ago
9th Degree Black Belt
0
Yes, make sure all current user registry settings are in their own feature and that feature is a sub feature of complete. If the application does not trigger the per-user registry settings when run in this way consider implementing Active Setup to create the entries.

Here is an article on Active Setup:

http://www.etlengineering.com/installer/activesetup.txt
Posted by: brenthunter2005 15 years ago
Fifth Degree Brown Belt
0
You are getting too complicated again!

All you need to do is create a SYSTEM DSN instead, as this is the equivilant of a User DSN for 'all users'.

All the entries for this DSN will be in HKLM\Software\ODBC\, especially the key \ODBC.INI\

Just add these registry keys to your MSI and this ODBC entry will be available to all users on the workstation.
Posted by: Qazmo 15 years ago
Orange Belt
0
I agree with brent, create a system dsn.
Posted by: brenthunter2005 15 years ago
Fifth Degree Brown Belt
0
@Qazmo - not alot of people ever tend to agree with me, are you sure?
Posted by: Qazmo 15 years ago
Orange Belt
0
ORIGINAL: brenthunter2005

@Qazmo - not alot of people ever tend to agree with me, are you sure?


Yus[:)]
Posted by: urban_diver 15 years ago
Orange Senior Belt
0
thanks for your help. I tried creating a System DSN. When logging on with an account that only has "user" perms. The application prompts you an error message indicating that a user dsn is required. When logging on with an account with admin perms. The application works fine.
Posted by: sejacru 15 years ago
Second Degree Blue Belt
0
If you have a policy, then try setting rights to the registrykey HKLM\Software\ODBC\ODBC.INI
Posted by: urban_diver 15 years ago
Orange Senior Belt
0
kkaminsk, that article worked like a charm!! Thanks!!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ