Glen,
Thank you for sharing your use of CA. I was thinking about following pretty much the same approach as you do, creating a cursor (with the use of CA) for each table and just use it as if I was using VFP table.
I have one concern however, when using CA compared to USE command. With USE you had the table opened and available pretty fast. With CA you have to fill the cursor with data when opening a form. Some of my customers' tables have up to 200,000 records. And I don't know what kind of performance hit this will have on my application.

Yet, I want to use CA so that in the future I can replace VFP database with SQL Server database. Lately troubleshooting data corruption in VFP tables is taking too much my time.

Dmitry

>>>Say I want to open 5 tables to be used in a form. Do I have to create 5 CA's in the DataEnvironment of the form, one for each table?
>>
>Dimitry.
> So far, my work with the CA's hasn't had to deal with Dataenvironment of a form. My mind is simple. I think of the CA as a Connection object, not a true Manager object. In my mind there is a difference. It connects to a table in the database and gets a record set for a manager object to deal with. One CA for each table. The Updates, Inserts & Deletes are simple. I create the cursors and let the manager object link them, manipulate them, update them, close them, as necessary. The CA is stupid where the Manager object using it is smart. Therefore I do use 1 CA instantiation per table. This will change in the future when the use is more intensive because it may entail too many hits to the backend for one operation. For now I've got to keep it simple.
>
>