>>But that forces you to stay in VFP

We're not arguing which DML is usuable across the most platforms. We're arguing which is the simplest and most direct approach for working with SP's. If it takes less code to achieve the same result, then I'm inclined to go with the simpiler approach. Simply put, in VFP you can call a SP, pass parms, get parms back, and even a cursor, all at the same time with one line of code. In ADO, you need to deal with all kinds of objects and collections.

>>using something like SQLExec, everytime I add a new output parameter to the >>SP, that line of code has to change

SPT statements can be built up as strings on the fly and macro expanded. That's about as flexible as you can get. However, most of time all you need to do is build up a parm list and insert it into the SP call.

Comparing ADO to VFP DML reminds me alot of the CD vs Record player argument. CD's are cool, they don't wear out, they can be programmed, ect. Trouble is, they sound like crap. A good record player will always outperform a CD by a wide margin. After all, digital audio is nothing but an approximation of a complex sinewave, whereas a needle vibrating in a groove of a record is a sine true wave generator. New and cool is not always better.

Charlie