Hi, Kevin.

>Some questions:
>
>1) When the object oCursor is destroyed, the table closes. Any way
>to make it persist?
>
>2) If the table can be persisted after the CA class is destroyed, can/how
>are changes submitted back to the data source?
>
>3) How would you impliment this? Obviously the structure required for each call
>to this code might be different. It seems inifficient to have to create a PRG
>for each table I want ot access.
>
>4) How would you use the CA in a multi tier environment? If I create a class
>based on session, with this code inside it, the resulting cursor is then in a
>different session. We don't use DBC's. All tables are free tables.

You may take a look at our Open Source TierAdapter Framework at:
http://sourceforge.net/projects/tieradapter/

This implements an n-tier architecture using CursorAdapter at the Data tier and XmlAdapter at the Business and User tiers. It was conceived as a training tool, but we used it for some applications, and then several others did, too. Sadly, the only documentation we have by now (beside the source code itself and the sample application) is a PPT you can download from my site (www.salias.com.ar/TierAdapter).

We are working on an article series about it for Universal Thred Magazine, but you can take a look now and se if you can get some ideas in the meantime.

A warning: the current version just supports VFP 9.0. Let me know if you want to get the previous one supporting VFP 8.0.

Regards,