Thank you for your help.

>Looks like from the thread you already got this answered.
>
>Ok, now my little bit of advice. I don't think DSN's are all that bad. Don't you still need to store the server name and database name somewhere? To me, the DSN is as good a place as any.
>
>BOb
>
>
>
>>Do I understand you correctly that the following should work:
>>
>>1. Create a connection and when VFP displays "Connection Designer" dialog box, check "Connection String", instead of "Data Source, userid, password"
>>
>>2. In the connection string field type (e.g.):
>>
>>"DSN=mydata;UID=sa;PWD=;DATABASE=mydata"
>>
>>And even though I DON'T HAVE SYSTEM DSN "mydata" in the ODBC Data Source Administrator, I would be able to connect to the SQL Server database "mydata"?
>>
>>Thank you for your help.
>>
>>
>>>Remote views require a connection in the DBC. However, you can set the connection up to use a connection string rather than a DSN. So, yes, you can use remote views without a DSN.
>>>
>>>BOb
>>>
>>>
>>>>I read in the book Client/Server Apps with VFP and SQL server that in order to use remote views to work with SQL server data you need to have 1)named connection in the DBC 2)DSN.
>>>>
>>>>I think I read in some message here that you don't have to have DSN. My questions are:
>>>>1) would it be an advantage to use the technique of working with SQL Server db without DSN?
>>>>2) how do you work with SQL Server data without DSN?
>>>>
>>>>TIA for any suggestions or help.