I'm aware of that, but it's VFP code. While Ken did a good job, its still not very fast, especially with large sets. I was hoping for something more low-level from them as promised, although I guess I could just write it myself...

>>ADO does work OK with VFP. The only issue is that "returning" an ADO recordset usually involves passing back a pointer, which creates a stateful object taht must remain in scope (see ASP, using server-side caching for data instead of RDS). Even though MS handles the persistence and threading issues OK, this methodology doesn't lend itself to even moderate size result sets.
>>
>>MS answer is RDS, which you are already investigating it seems. RDS is a client-side cache of the data. But RDS doesn't seem mature yet.
>>
>>At one point MS was making vague promises about being able to pass ADO recordsets to VFP cursors and back. This would have made ADO a much more compelling approach.
>>
>
>You can convert ADO to VFP cursors and back again. There is full code available on Ken Levy's web site, www.classx.com.