Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-10-22 : 08:32:00
|
| Ashraf Chaliparambil writes "I created a User DSN and tried to access using connection string (Str = "ODBC;DATABASE=CDMDemo;UID=" & TxtUserID & ";PWD=" & TxtPwd & ";DSN=CDM"). Now my problem when I tried the sql user with I created the ODBC is getting connected. But with any other user it is not getting connected. When first trial getting failed then it calls the SQL server login window and it accepts the user. How can I call the SQL login window. Why this is accepting only the default user.Hope u can help me in this regard.Thanks and regards.Ashraf" |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2002-10-22 : 10:59:51
|
| "I created a User DSN"I think the problem MAY BE here....you may need to create the DSN as a SYSTEM DSN.....(by my understanding USER DSN are specific to whatever user is signed onto the PC...whereas SYSTEM dsn's are usable by all users of the PC...) |
 |
|
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
Posted - 2002-10-22 : 14:48:53
|
| Yes, system DSNs are most effective when created on the server side. Such a system DSN offers easier access when coding pages (in my case, ASP pages) that run against the server. If you create a system DSN on the SQL Server, then you can refer to this DSN by one word name in your code and thus avoid the long string with connection path, userid, etc. |
|
|
|
|
|
|
ODBC User DSN