>With the cursor location at client side for the connection object, both samples fetch all rows at that time, putting the test on the level with SPT. It is not the same as a VFP cursor of course, but as I wrote in my reply to Jim Nelson it depends on what your application needs are. For some applications it is not necessary to have a VFP cursor when you can access the data from the ADO recordset directly. With the exception of the report writer ADO data can be consumed from a recordset in VFP.
>I'm not going to argue on looping the whole recordset, I know that a SCAN on a VFP cursor will be faster. Not by a whole lot if you use WITH.. ENDWITH on the ADO recordset, but then that is another subject altogether. Depending on the application I wouldn't use ADO if I needed to scan a large result set.

I believe, if you retrieving a large result set, then you need all data in it. Therefore you'll loose time on accessing all data from ADO client cursor later. If only a small part of result set is required, then result set may be limited by WHERE clause and SPT still will be faster (with a small recordset).