For a record at a time, this is a good alternative and the one I would suggest. But if you want to display multiples records in a grid, an ADO recordset is a much better way of passing informations, IMHO. Having to call MoveNext on each record would take time since there is a performance penalty to take when pasing informations between tiers. It much less costlier to pass an object (ADO) than a series of records via MoveNext.

---

>I've never done this, so this might be just another wild idea, but here goes anyway. How about simply dumping ADO altogether and having your VFP COM object do the work? Methods like VFPObject.Fields("Somefield") can easily be made, or MoveNext, MoveFirst, etc.
>
>I've never used ADO other than in VB, but I just can't figure out what are the advantages of using ADO compared to what VFP offers.
>
>As for updating the data (without ADO), updatable views should work I beleive, or you could build your UPDATE SQL statement using GETFLDSTATE().