>I decided to start a new thread since this has gone beyond my initial question of why XMLTOCURSOR is so slow.
>
>Anyway, if I can't use XML to get data from one object to another, what should I use? I've got one object that deals with things locally using a cursor and another that gets the data from the tables. I'd rather not have the remote data object write straight to the local cursor because that seems to be defeating the point. I'm lost as to how I should be doing it, though. Or should I just have it use the same cursor? How is it normally done?
>
>Thanks,
>
>Michelle

Disconnected ADO recordsets work well for data transferring between objects, and are especially suited for marshalling across process boundaries.

I have used them mostly for distributed n-tier applications, and have not had any problems with them. The only two cons that I find is that I need to be thinking object model instead of normal VFP data handling, (that is not necessarily a bad thing) and the speed tradeoff compared to a VFP cursor.

Just my .02