>You can pass an ADO recordset as a parameter to different methods and objects, and you are refencing the actual data. You can even marshal a recordset from one component to another...

This is advantages between COM objects. You can also pass session objects as parameters to achieve similar results if you design a session class to accomodate an comprehensive dataenvironment - one that goes way beyond that of a form.

One problem I have with ADO is the inflexibilty associated with DataMunging legacy data from various sources (e.g. COBOL systems). Sure, I could continue to create temp cursors after parsing all the bizarre files and record formats and then update ADO recordsets from the cursors thus mixing VFP cursor technolgy with ADO, but why? In fact, this is the reason that I've stayed away from VB - no way can VB compete with VFP on this stuff.