Keep in mind that NT authentication means SQL will use your Windows user credentials for authentication (period).

SQL authentication is a completely different animal - users and passwords are created in SQL Server. A windows username and password will not work in SQL authentication unless you have manually added that user and password to SQL Server, and you have given that user rights to the database/objects it is accessing.

>Hello,
>
>The application and SQL 2005 Express are loaded on the same Vista Ultimate computer. Since I can connect using NT Authentication, I presume I ought to be able to connect using SQL Authentication provided the username and password are typed in correctly -- I have typed them several times and made sure to be carefull to type them correctly. TCP/IP is enabled.
>
>It seems as though I should be able to "TEST" the connection when I type in the username and password when I go to properties in the Server Node. Any idea why I error out in there? I am in SQL 2005 Express manager -- you would think I should be able to connect!
>
>Thanks for any other suggestions you might have,
>
>TFISHER
>
>>Several questions arise:
>>
>>Are you connecting locally or remotely?
>>Is your firewall configured to allow connections to SQL Server?
>>Can you connect using a data link file (udl)?
>>Can you connect from VFP or VS?
>>Did you check the connection settings in SQL Server Configuration Manager and Name Pipes and/or TCP/IP protocols are enabled?
>>Are you sure the password you're sending is the same one you type when creating the user?
>>
>>It'll also be helpful to see your connection string but when dealing with connection errors these are the things to first check.
>>
>>Enmanuel
>>
>>>Hello,
>>>
>>>When I right click on the database instance and go to properties, Authentication is set to SQL Server Authentication. I do not have a username and password set there because I pass that inthe .exe of my program.
>>>
>>>Interestingly enough, when I do put the username and password in, then click the Test button, I get a SQL failure! The failure is Error: 18456, Login failed for user 'affmaker' which is the username I have specified in the Security Logins. In the Security Logins, I created the user 'affmaker,' selected SQL Server authentication, entered the password and confirmed the password, then I set the default database. In Sever Roles, public is checked. In User Mapping, the Database is checked with affmaker listed in the User column and db_owner and public are selected as Database role membership at the bottom. Nothing is listed in Securables.
>>>In Status, Grant is checked at the top for Permission to connect to database engine and login is enabled. Interestingly enough, Status for SQL Server authentication is greyed out with no check in the greyed out checkbox.
>>>
>>>Again, all of the above is on a Windows Vista Ultimate machine.
>>>
>>>Any ideas what I need to check to get SQL Authentication to work?
>>>
>>>Thanks,
>>>
>>>TFISHEr
>>>
>>>>From Management Studio Express right click the server node in the object explorer, select properties and click on security. It'll give u what you want.
>>>>
>>>>
>>>>
>>>>>Hello,
>>>>>
>>>>>When I installed, I made that selection. Where do I check to make sure it is set to Mixed Mode?
>>>>>
>>>>>
>>>>>>>Hello,
>>>>>>>
>>>>>>>When I connect to my SQL 2000 database using SQL Authentication, I give the user dbo privileges and can log in without a problem. In my SQL 2005 database using SQL Authentication, I give the user dbo privileges, but I get a SQL error. The username and password are built into my VFP application and are passed to SQL at runtime.
>>>>>>>
>>>>>>>Do I have to give the user additional privileges in SQL 2005?
>>>>>>>
>>>>>>>Of course, if I use NT Authentication, I can get in to SQL 2005 without problem. But, I want to use SQL Authentication.
>>>>>>>
>>>>>>>Thanks,
>>>>>>>
>>>>>>>TFISHER
>>>>>>
>>>>>>Are you sure your SQL 2005 is set to mixed-mode authentication?