>>I'm now learning to use ado for developing n-tier aplications with VFP. I'm using vb when i don't know things(intellisence) and then do the same in VFP. Here is my problem.
>>When i refer to an ado recordset in the recordsource of a grid or when i refer to a recordset-field in the controlsource of a textbox, the error 'datatype mismatch' occur. Ofcource, a VFP cursor is not an object and an ado recordset is. I could use the microsoft data objects that vb uses, but that is solving the problem bypassing VFP again. An other way is trying to make the subclassed controls using the ado objects by not using the controlsource or so ever, but that takes to much time, considered every data aware control has to be prepared.
>>so, my question is:
>>
>>When does VFP gets really object-orriented with his data?
>>Does somebody now how to solve these problems in a simple way (maybe i look at it to hard).
>>Does VFP7 has new things what this matter?
>>
>>Thanks in advange.
>
>You can't use an ADO recordset for a grid. You need to convert it to a cursor first. The VFPCOMM.DLL has a method that will do this. You can bind a textbox to an ado rs. How are you doing this?

Converting a rs to a cursor and back is an extra step downwards in performense and making the midle-tier a bit special just for vfp, although this could be done in the ui-tier. I think not only the grid but also the listbox and combobox needs a conversion to a cursor, so why not converting every rs to a cursor. This is not the meaning of using ado.