Well, I don't agree with Sergey on that. ODBC requires many more system resources, which leaves less for VFP to work with.
Before figuring out how to configure the CA to use ADO, you should understand how to use ADO directly. You may already know this, but just in case, see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnfoxgen/html/adojump.asp?frame=true>Hi,
>
>Thanks for the response.
>
>"I'm don't quite understand what you want to do. If you have a VFP 8.0 app, why not access the data natively? See my other comments interspersed below..."
>
>I'm just starting to change my framework to use cursor adapters and yes, you're very right it seems that I need to use Native, my framework was designed to work with a connection string using odbc but it seems that these changes are going to flow and work just right. I just want my framework to be able to use any of the 3. I'm guessing the Native is supposed to be faster...
>
>So in order to make it work using OLEDB I need to do these 2 things?
>1.- In my connection string I need to specify that it's oledb
>2.- In the Cursor Adapter I need to specify "ADO" for the 'DataSourceType'
>
>Is this correct?
>
>I was a bit confused about which one is faster, using ODBC or using OLEDB (where I have to use ADO as a wrapper if I understand correctly), and Sergey mentioned that ODBC is faster than ADO which seems that I have to use in order to use OLEDB. Could you clarify?
>
>Thanks again!
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer