Yes, XML can be really slow when dealing with large data sets.

>I'v asked something like this before, but I need more opinions.
>
>I want to create a 3 tiered app. My opinion is that ADO is perfect
>for moving data between layers.
>
>It would be nice to have VFP tables to bind the form's to. Criag B.
>and I discussed binding ADO RS's to the form. We also discussed using
>CursorAdapters.
>
>At the last DevCon, I had one speaker advocate using the new CursorAdapter
>class to do the following:
>
>1. The UI sends a query to the business layer
>2. BusObj validates query parameters and calls into the data layer.
>3. DataObj receives query request, opens and retrieve the data, then uses
>a CursorAdapter to convert the data to XML, then returns the XML dataset to
>the BusObj.
>4. BusObj sends XML dataset back to the UI.
>5. UI uses a CursorAdapter to convert the data back to VFP tables.
>
>This seems like alot of work, and must be really slow when large
>datasets are returned. (100K records for example).
>
>Seems to me, that ADO is perfect for the job.
>
>Anyone?