I agree and it works. But the customer tells me is that it started working only after he did the following two things:
1. In SQL Server Configuration protocols for SQLServer he Enabled Named Pipes (it was Disabled by default)
2. He also set up System DSN on the application server (where app resides) and unchecked the "dynamically determine port".
I don't understand how the no 2 above made the difference in my application connecting to the SQL DSN-less.
>1433 is default SQL Server port. Your application should work as is.
>
>>
>>The client informed me that in order for my VFP application to connect to the SQL Server it has to be done via DSN with the option "dynamically determine port" to be unchecked since the SQL server is listening on static port 1433. My VFP 9 application connects to the SQL Server via DSN-less ODBC connection. My question, if I include the SQL Server IP and the port in the connection string, should it work just like it would with DSN? For example, if I include in the connection string the following:
>>
>>"ADDRESS=175.33.33.09,1433"
>>
>>should it work? TIA.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
