>>Hi Antonio,
>>Initially only Windows Authentication was enabled. I changed it to the mixed - Windows or SQL Server authentication.
>>Then in the Security of the SSMS I created a login name. Gave it a name and a password. Pretty simple.
>>Then I added this name to the User of the DB. And I set up in the Owned Schemas and Memberships this user as the owner (I later added a couple of other roles, since I thought that owner was not enough).
>>I closed SSMS and opened it again (just in case)
>>The connection string has the server name, DB name, Integrated Security set to 'false'. The VFP 9 won't connect to the server. The message says that login "myuser" cannot connect to the SQL Server. Errors:
>>28000
>>18456
>>When I change - in the connection string the Integrated Security to 'true', connection works.
>>
>>I have done this many times before and it works (with Integrated Security 'false'). But somehow so far, I cannot make this work.
>>
>>Thank you.
>
>Ok, Dmitry, so can you enter SSMS with the new user's credentials? And, once inside SSMS, can you access the database?

Good suggestion, Antonio. I tried it but get the following results:

Cannot connect to SERVERNAME
Additional Information:
A connection was successfully established with the server; but then an error occurred during the login process.
(provide: Shared Memory Provider, error: 0 - No process is on the other end of the pipe) Microsoft SQL Server,
Error 233)

No process is on the other end of the pipe

UPDATE: Problem Resolved. The TCP/IP did not have port specified. I entered 1433 and now I can connect.

Thank you