An approach used by the Mere Mortals framework is to access backend data, like SQL Server, with remote views from the business objects. Then the business objects can convert the resulting VFP view to ADO or XML for those clients that request the data in that format (ASP, VB, etc.). But the VFP front end can still access the data as VFP data, rather than ADO.

>I am using VFP 6 as a front-end to a SQL Server 7 database in a new application, and I have been working with ADO objects for the data access mechanism. After exploring views and SQL Pass-through, these seem to be a bit easier to use for me.
>
> I have created a set of my own data objects as wrappers for the ADO recordsets, and this allows me to do things like validation and business rules before actually changing table data. I haven't thought of a good way to deal with parent-child relationships in the user interface yet, however. I would like to be able to get an ADO recordset (as a child in a relation) into a grid, for example, bound to a parent key, much as SET RELATION works in regular VFP tables. As an alternative, there is a way to load ADO data into an array, which could be used to fill a list box or something. I was just wondering if I am missing anything obvious here. Like any way to bind a grid to something other than a cursor.
>
>Any help would be greatly appreciated, or even a good single-source for ADO object documentation. I got a good head start with an MSDN article called 'ADO jumpstart for VFP developers'