I don't say that is not possible/never work. We distribute a program with ADO/VFP6(tested later with VFP7, but for several reason keep in 6).


This was using COM+/DCOM/MTS, and very later we found that exist hard to resolve problems with this setup, mainly is impossible send a recordset by ref then return the same, etc... and is necesary go to xml, arrays, cloned recordset in a multi-tier solution... The performance is not so good. Anyway is posible do a workable solution and if is necesary only a read-only recordset solution then realy is not so problematic (=work in the first try). But for a full-database aplication is a bad chose.

All people that i know that chose this route, later move to arrays, xml, custom objects, or a mix of them. Is for that reason that is best use in the first time array/custom native vfp object and cursors....