>Here's a possible scenerio:
>
>I have a multi-tier app. VFP GUI, BizObj, and a SQL Server data layer. The
>BizObj and Data Layer will be compiled into VFP COM objects.
>
>So the GUI passes a query into the BizObj, which passes it to the data layer.
>Since the data layer is SQL Server, it would need to have a way to pass the
>data back across COM boundries through to the BizObj, so naturally ADO is used.
>
>Then the BizObj passes the ADO RecordSet back to the GUI. The GUI uses a CursorAdapter
>to convert the data to VFP tables, which are bound to form controls.
>
>On the reverse, the data from VFP tables is converted back into ADO, then passed through
>the BizObj for validation to the data layer and updated into SQL?
>
>Sound about right?

Kevin,
One other scenario is to use XML instead of ADO. SQL Server 2000 supports the extraction of XML using the FOR XML clause of the SELECT command. You can use the OPENXML T-SQL function to convert any received XML into a result set and insert/update based on that. See SQL Server BOL for more information.

The CursorAdapter/XMLAdapter will convert XML into a VFP cursor and you can work with locally.

Just another way to skin a cat ..er..Fox. ;-)

Regards.