×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

ODBC and user rights

ODBC and user rights

ODBC and user rights

(OP)
I have created ODBC sources on NT workstations that connect to Microsoft SQL 7.0, logged in as workstation Administrator.  On most workstations, everything is fine.  Occasionally, however, on some machines, ODBC sources created under one user (eg. Administrator), are not available to workstation users: they get an error stating that the source does not exist.  Furthermore, while logged in as the user, I try to create the source that apparently does not exist, the system tells me it already does.  Lastly, if I do create a new source logged in as the user, the Administrator cannot see it.

Usually, I end up logging in as Administrator, deleting all of the sources, and recreating them under the user login.  But then other users cannot login to that workstation and use the data sources.

I hope I've expressed my problem clearly.  If anyone has any ideas, please respond.  It is very much appreciated.

RE: ODBC and user rights

If you have the option, try using "DSN-less" connections that use connection strings rather than pre-created DSNs.  These can be used by clients such as ADO and Visual FoxPro.  An example:

driver={SQL SERVER};SERVER=Discovery;UID=myid;PWD=mypwd;DATABASE=mydb


Robert Bradley
http://www.foxdev.com/
http://www.agrainofhope.org

RE: ODBC and user rights

(OP)
Hi,

Thanks for the reply.  Unfortunately,  I don't have any control over the connection.  The software is ACCPAC for Windows accounting software, and it uses the ODBC entry to connect to the SQL database.

Loading all the ODBC connections under the local user (not a local admin) allows the connection to work.  Making the user a local admin also solved the problem. It does seem to be a permission deal, but pretty obscure.

RE: ODBC and user rights

Are you creating "User" dsn's which are only available to the user who created them, or "System" dsn's which are available to any user who logs in to the workstation?

Gladys Clemmer
gladys.clemmer@fifsg.com
 
 

RE: ODBC and user rights

(OP)
Hi,

Thanks for the reply.  These are being created as System DSN entries.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close