Start by getting my CA VCX Builder and read the comments at the beginning of the CABuilder PRG file. Also download my samples and see how that works. Just click the FoxPro Tools link at http://www.mctweedle.com

Once you have your CA classes, when you upsize to SQL Server, all you have to do is change the connection as long as the tables in SQL Server are the same structure as your VFP tables [e.g., all the VFP field data types are mapped properly to the SQL Server field data types].

Using the CA with ADO will create a local cursor with the alias name specified in the Alias property of that CA.

I also provide a "parameter" property in the CAs created by my CABuilder where you can specify a SelectCmd filter to reduce the number of returned records.

>I want to use a CursorAdapter in an app Im working on to pull data
>now from Native tables and later on switch to SQL server.
>
>I'd like to do this in a DLL, so that I can just swap out the DLL
>at coversion time.
>
>Question 1:
>From what I see, pulling large amounts of data, say for a grid, are
>not a good idea. So how would I then pull, say, all records for customers
>in Californation without taking a bandwith hit?
>
>Question 2:
>Assuming I use ADO for passing the record, how do get the data into
>native tables? I'd like the interface to use native tables. Then I only
>have one place to go to switch from Native to SQL.
>
>Question 3:
>The cursoradapter seems to have properties that are inflexible. If I want
>to change the updatable field list, then I have no choice to pass this into
>my query method. How do I truly subclass this without haveing to pass many
>parameters to each query function?
>
>Many Thanks!