>>An educated guess: a 3 meg ADO recordset will translate into
>a MUCH larger XML set because of the repetitive tags needed
>for XML. The extra space could translate into extra processing
>time. I think even a tab delimited text file would be much more
>efficient.
>
>Totally off topic, but I notice how processing time is a paramont
>factor on VFP thread versus VB disucssion groups. Is it that
>VB is just too slow (in data processing) to even care?
Well, on this thread in particular, because that's the whole goal. The originator (of this branch anyway) was complaining that the time to process a 3 MB ADO recordset to a VFP cursor using standard methods was unsatisfactory, and was looking for faster alternatives.
To answer your question- well... I don't know. VB doesn't have native data access, so as a far as _data_ processing, we can't compare apples to apples. String processing though, VB is pretty good at, but every head to head test I've seen shows VFP blow VB out of the water.
Erik Moore
Clientelligence