>>>
>>>PS: Go to command window, type:
>>>dx[spacebar][enter]
>>>to invoke data explorer. There create a connection. OPen a code window and drag&drop a table from sql server on to that code window.
>>>VFP creates an ADO based CursorAdapter for you (but the utility didn't take into account or didn't know schema you may need to edit scripts in SP1- or the code generating those scripts from options)
>>>
>>
>>Sergey explained to me that you meant VFP Command Window. And I tried it. This "dx" (Data Explorer) is very powerful; I never knew it existed (among many other things in VFP <g>). And I noticed that when I dropped a table on a code window, the connection string created by VFP has "SQLOLEDB.1" set as a Provider. In your sample code you used "SQLNCLI10". Is SQLOLEDB.1 just a different name for "SQLNCLI10"?
>>
>>Thank you.
>
>SQLOLEDB.1 or SQLOLEDB is the old SQL 2000 driver. That is version number of the OLEDB driver (the one after dot). You can leave out that kind of version number (I leave out so it would pick latest of that driver but in this case it is SQL 2000 driver which is old and there is no newer version of it). SQLNCLI10 is the correct driver name (provider name to be precise-in ADO world you use data "provider") for SQL 2008. It is the latest driver as of today. Check and bookmark www.ConnectionStrings.Com. There you would find virtually any data connection's ODBC/OLEDB/.Net ... connection strings.
>Cetin

Thank you for the explanation.