>Hi Jess:
>
>>>how would it be that it can not be subclass?
>
>The ADO client side recordset object can not be subclassed to extend it functionality beyond what is offered in stock recordset object. It sounds like your using VFP objects to create wrapper classes that adds some new functionality to stock recordset object, but IMO, its a not the same.
>
>>>JVP confirms it that ADO is better when it comes to SP calling.
>
>I argued this point with him and I still believe that SQLEXEC() requires much less code to call a SP and receive a return value. Also, SQLEXEC() statements can be built up as strings then Macro expanded which is great for builing reusable data objects. Try doing that with ADO.
>
>Also, with ADO can you call a stored procedure, pass in parameters and recieve an output parameter and a cursor at the same time? I don't think you can do that with ADO, but you can do it with Fox.

Macro expansion is one advantage that I can think of on SPT against ADO.
Using Command object you can do a lot of things in the data including calling SP that requires passed parameters.

Well, bottomline is, and I stated already in my previous thread: SP, ADO, SPT, and RVs have its own strengths over one another depending on what we want to do and where we are more convenient and productive. To me, I started building COM DLL using both and I find it nice to have both technologies applied.

more power.