>Hi Rick,
>
>Im new in those XML things. And i know you work a lot with XMLTOCURSOR() from WebConnection. I dont know but maybe u develop this function in WebConnection!?!
>
>Now, read the following an tell me what u think.
>
>*-----
>Your can use XMLTOCURSOR() with Stream but with the content of the object. In the doc on XMLTOCURSOR(), u can read this line:
>
>
You also can specify return from a SOAP method call, XML from the XMLDOM, or an ADO stream".>
>I read somewhere that the XMLDOM is not functional in C++, or VFP. Just in VB code. So it's not a great container for me. But Stream is working well.
>
>My only mistake is trying to use the object oStream directly in the first parameter. I have to use the ReadText method to acess text inside the oStream object. Just like this:
>
>
> XMLTOCURSOR('oStream', "MyCursorName", 1028)
>
> XMLTOCURSOR(oStream.ReadText, "MyCursorName", 1028)
>
>
>This is working!
>
>Try the following little program
>
>
>oConnection = NEWOBJECT("ADODB.Connection")
>oStream = NEWOBJECT("ADODB.Stream")
>
>oConnection.Provider = "SQLOLEDB.1"
>oConnection.ConnectionString = ;
> "Persist Security Info=False;User ID=sa;"+;
> "Initial Catalog=Shipping;Data Source=FS01"
>oConnection.open
>
>oRecordSet = NEWOBJECT("ADODB.RecordSet")
>lSelect = "SELECT * FROM CUSTOMER"
>oRecordSet.Open(lSelect, oConnection)
>
>oRecordSet.Save(oStream, 1)
>
>XMLTOCURSOR(oStream.ReadText, "MyCursorName", 1028)
>
>* Release objects
>SELECT MyCursorName
>BROWSE
>
>With a table of 40 records there is no problem. I have some tests to do with bigger tables today.
>
>I give u news on this,
>
>Thanks,
>
>Francois Durocher
Francois,
Rick knows something that I can miss easily I believe.
For working ones xmldom works too :) See my reply to Rick.
Cetin