>I think one place in VFP where ADO may prove useful is in middle tier components. You can't return a VFP cursor from a component, but you can return an ADO recordset. This is particularly good for situations where you want to create middle tier objects that can serve data to multiple clients (e.g., VFP, ASP, VB).
>
>I certainly wouldn't recommend using ADO as a replacement for VFP's data manipulation language. Especially now when most ADO calls have to through ODBC anyway.
>
>>ADO in VFP is a solution looking for a problem IMHO.
>>
>>And I kinda agree with the second statement...don't bother me with the babysh*t, I'm too busy servicing 300 concurrent users in a monster client/server app....
>>
>>Then again, VB people tend to *love* wasting time with little itty bitty stupid things...VFP people generally don't.
Yes but still it is difficult to manipulate the recordset because you have to fetch the record one by one. It would be perfect if we could "link" a native foxpro cursor with the recordset. Or this can allready be done ???