Hi Mark,

I think I understand the basics of the CA class. I want to 'finalize' my
thinking before I hit the keyboard.

My thinking calls for a typical n-tier app with a VFP front end linked to
variable data sources via cursoradapters built into COM objects.

I favor the COM approach becuase, if designed correctly, I could conceivable
drop a replacement COM DLL over an existing one and have a different data
approach in use. VFP to SQL to XML with a simple file replacement.

One question still bothers me; ADO is great in the respect that it can be passed
as an object parameter. But what about a CursorAdapter that retreives data from
SQL? The following conversion scenerios seem to be necessary:

FROM THE GUI:
Field values store data to a table/cursor/view
Table/Records converted to ADO
ADO Recordset passed to COM object
Validation
Pass to data class
Data class uses CA to convert to native data type
Write out data

TO THE GUI:
GUI creates a blank ADO recordset
ADO recordset passed by GUI with a query to COM class
COM Class handles Validation for access rights/query integrity, ect...
COM Class passes ADO Recordset to data class
Data Class runs query, fills and returns ADO recordset to COM class
COM class returned recordset to GUI
GUI uses CA to convert data to a table/cursor/view
Data is displayed

I welcome your thoughts