Thanks for the help Vlad. The key was in the suggestion to let VFP generate the connection string and then move it into our ASP environment.

Have a great weekend!

Dave

>Hi!
>
>DRIVER={SQL Server} - where you try to connect to: SQL Server or VFP database?
>
>You can get correct string by playing around the connection creating in the VFP database. Create it for VFP database using DSN, than switch option to use connection string after you tested a DSN connection. VFP will populate string for you from the DSN. You can use this string also for ADO to connect.
>
>HTH.
>
>>We are putting together an ASP front-end using ADO and would like to access our VFP DBC for inquery and eventually updates using a DSNless connection.
>>
>>The same functions are being performed on our SQL Server applications using:
>>myDSN="PROVIDER=MSDASQL;DRIVER={SQL Server};SERVER="&Application("SQLServerName")&";DATABASE="&Application("DBName")&";UID="&Application("DBUsername")&";PWD="&Application("DBPassword")&";"
>>Set DataConn = Server.CreateObject("ADODB.Connection")
>>DataConn.Open myDSN
>>Set rs = Server.CreateObject("ADODB.RecordSet")
>>rs.Open strQuery,DataConn,1,3
>>%>
>>
>>I have looked thru this site and some others and can't seem to find the syntax to modify the myDSN and rs.Open lines and any war stories to say DO or Don't do it......
>>
>>Thanks in advance for the help!
>>Dave