>>Hi,
>>
>>I have been having an issue with a new customer as far as connecting VFP 9 application to SQL Server. Here are the details of the environment and the problem:
>>
>>The VFP 9 application resides on one VM and SQL Server on another VM box. My VFP 9 app connects to the SQL server via ODBC DNS-less connection. The SQL server is set for both Windows authentication and SQL Server authentication. The VFP 9 application connection string uses SQL Server authentication.
>>
>>When I RDP to the VM where VFP 9 app reside and start the VFP 9 application it connects to the SQL Server, no problem.
>>
>>When customer, who's desktop is on the network, starts the application, connection fails. And when I look at the SQL Server error log I don't even see entries of his attempt and failure to connect.
>>
>>So I thought it was a firewall issues. But the local IT guy says that the Windows firewall is Off (on the desktop where they are trying to start the app).
>>I asked them to ping the SQL Server box IP from the command prompt of the desktop and they say that works.
>>
>>What else could I ask them to check on the desktop? Any suggestions?
>>
>>TIA
>
>Try to create an ODBC connection from Control Panel->Administrative Tools->ODBC.
>Also try to force the connection to use TCP/IP or Named Pipes. Put NETWORK=dbmssocn (for TCP/IP) or NETWORK=dbnmpntw (for Named Pipes) in your connection string.

First, thank you. Just to clarify:
1. I should not use both, the TCP/IP and Names Piptes, just one? right?
2. The values 'dbmssocn' and 'dbnmpntw'; are this literally what I put into the connection string or I have to use "my" sql values?

Thank you.