Several problems with the RSToCursor Method:

1. The Recordset is fabricated - not updateable
2. When working with non-vfp data, many data type conversion errors can be
encountered.
3. Long column names get truncated
4. Can be slow


In fact, this is a fairly straightforward operation, as long as you have SP 3. I tested this stuff on several machines, and have encountered no problems. Hard to tell what else could be occurring without some further info..

>>I created a form with the oleDB Grid, FlexGrid, and HFlexGrid, trying to make any data show up. My ADO rs did end up with records. but as I mentioned when I set the DataSource property = to my ADO object no data showed up in the form at run time, I then set the DataSource property = the Character name of my ADO object and I kept getting data type mismatch.
>For the MS Datagrid, you need to include the ADO data control. The grid binds to the ADO control and you set the record source for the data control to your ADO recordset. I have it working with VB, have had problems getting the ADO control to work in VFP with several activex controls.
>There are other options not as straightforward as having the option to bind the recordset directly, one being converting the RS to VFP cursor with VFPCOM utility.