>>>>>>>>Hi,
>>>>>>>>
>>>>>>>>When a user tries to connect to SQL Server 2008 (from my VFP 9 application) he gets error:
>>>>>>>>
>>>>>>>>

>>>>>>>>SQL Server Error 10060
>>>>>>>>[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpenConnect())
>>>>>>>>

>>>>>>>>
>>>>>>>>The connection string I set up has my SQL Server ID and Password and I could connect (at least last night) without any problems. And he (this user) is supposed to connect with these credentials but something does not work. One thing I don't understand in the above error is [DBNETLIB]. What does it mean? TIA.
>>>>>>>
>>>>>>>Looks like DBNETLIB is the DSN name. Is it all information you captured about the error? Did you try running SQLExec using the same parameters as your app?
>>>>>>>
>>>>>>>BTW, did you try google this error?
>>>>>>>
>>>>>>>Say, http://social.msdn.microsoft.com/Forums/en/sqldataaccess/thread/49456b68-af1d-4de2-81aa-47e5325ca628
>>>>>>
>>>>>>The rest of the error was kind of self-explanatory "SQL Server does not exist or access denied" There is also SQL Server Error 17.
>>>>>>
>>>>>>The connection string should be using SQL Server authentication (not Windows authentication). In this case, does DSN name play any role? I just don't understand if I need to worry about the [DBNETLIB] at this point or there is another thing that prevents the access.
>>>>>>
>>>>>>The one thing that the link you sent me points to is possibly a firewall blocking the access. But the user is on the local area network where the SQL Server installed. But it could be the reason still.
>>>>>>
>>>>>>Thank you.
>>>>>
>>>>>
>>>>>I don't think DSN name plays any role. The simplest test is to try accessing SQL Server using that user's credentials. Simply test that DSN for that user.
>>>>
>>>>Thank you.
>>>
>>>If that user has 64 bit OS, make sure that DSN is created with the 32 bit ODBC.
>>
>>What I don't understand is how to test that DSN user. I suppose I have to be on his computer to test it, right?
>
>Yes. From his computer you need to invoke odbc application and test that DSN. Make sure to invoke 32 bit version if he is using 64 bit OS (I've been beaten by this problem myself recently).

Thank you for clarifying. I will ask the user what OS he is running.