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 - 2003-07-11 : 07:12:47
|
| Wimpie writes "I've tried searching for this but I can't get it to work.To give you some background, we are running a 3-tier app using a SQL Server database. We can't get the program to work out of Administrator mode so we need to install both the client and server components on the client machine and then access the database directly. This is just a short term solution until we get the other problem sorted out. The server is running Windows 2000 with SQL Server 2000 and not running on a domain. No service packs installed that I know of. The client is running Windows 2000 Pro with MDAC 2.6 installed. I created a new datalink file and set up the link to the SQL Server machine and database. I tried creating a user in SQL Server so that SQL security is used rather than Windows security. Either way I keep getting an error when clicking the Test button. I can't remember the error exactly but it goes something like: Login "username" failed: Not a trusted (connection / user / etc)... I must go back to the site on Monday and get the system working or we lose the deal. I'll try to get some more resources and help on my side as well." |
|
|
Andraax
Aged Yak Warrior
790 Posts |
Posted - 2003-07-12 : 11:21:08
|
| Hi!When you set up the DSN, you have to specify that you are using SQL Server Security, and provide a username and password. And of course the SQL Server must have mixed security mode and the user set up with the correct password. |
 |
|
|
|
|
|