>>>One of the difficult things for a VFP developer when they start to use VB is the lack of a data cursor. A cursor is a table of data records. If I use ADO I get similar functionality but what if I have an n-tier applications that has passed some up some XML to the VB front-end. What do I convert the XML into so that I can manipulate it with VB?
>>
>>Depends on the nature of the XML. The app I am working on now passes XML from the data access tier... I started the project using a wwXML style XML document, but then decided to just persist ADO recordsets to XML and pass those. You can then use that XML to create a RS from a VB or VFP client. I also wrote a function that converts ADO XML to a VFP cursor, so I have the best of both worlds.
>
>Sorry Erik, I don't understand your answer. Can you point me to any resources? In particular I don't understand the difference between an XML document and "persist ADO recordsets to XML". Also what is "ADO XML"? Is this a special kind of ADO or XML?

As of ADO 2.5 (I think), you can persist an ADO Recordset to an XML document that can later be used to recreate the Recordset:

In VFP, this might look like:

oStream = CREATEOBJECT("ADODB.Stream")
oRS.Save(oStream, adPersistXML) && adPersistXML = 1
lcXML = oStream.ReadText()