Gene...

FYI, when responding to a message sent to somebody else, it is good practice to begin with PMFJI (Pardon Me For Jumping In)....< s >

>The are grids that bind directly to ADO and build browse type
>windows just like the grid in VFP. But there much more coding
>in ADO then in VFP!!!

You will be able to use these grids in the next VFP release. Then again, browsing data is not the reason to use ADO.

>There really isn't any reason (from what I can see) to use
>ADO from VFP since VFP form objects can't bind to the ADO
>object model. Using VFP remote views\SQL PassThrough is
>much more productive.

This is not true. Textboxes can bind directly to the Value property of a Field object. Also, if you are engaged in automation operations, or need to pass data to/from a VFP DLL, an ADO recordset is the most effective way to accomplish that task.

FWIW, remote views are a waste of time. Anybody who has done any C/S work of note knows this to be true. As for SPT being much more productive, as far as creating VFP cursors automatically, you have a point here. However, the issue of how you pass data to other components remains an issue. ADO allows you to work with objects and OLE-DB providers, which is WAY more productive than SPT.

Finally, unless you have worked with ADO to any degree, how would you know if Remote Views/SPT is more productive?

Just a question....