ODBC and user rights

[robeau]

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.

 

[foxdev]

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

 

[robeau]

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.

 

[dzdncnfsd]

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

 

[robeau]

Hi,

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