As of VFP SP3, you can now bind several activeX grids to ADO recordsets in forms. And you can even make the OLEDB grid editable, and make it smart enough to write user changes back to the back end. YOu have to jump through a few hoops to get the insides of the grid configured at design time, but it's definitely doable.

You have been able to bind textboxes and the other simple databound controls to ADO field objects for some time now.

And now with VFPCOM, you can write your own code that will fire on ADO events. This gives you the ablilty to write a VFP class that knows how to bind itself to a ADO recordset object and you can code to your hearts contents just as if you are directly programming in the the COM object.

We're coming a long way with support for ADO already.

>Maybe the next version of VFP will at least contain the ADO support that VB has. That would be a good start.
>
>>ADO seems like a really good solution for C\S development, I've been doing some reading and I like what I see. To be useful though, we either have to be able to reliably convert to and from cursors and recordsets or use ADO compatible activeX controls in out forms. I'm hearing alot of conflicting reports on the success of these options. I hope someday ADO is viable with VFP.
>>
>>Charlie