>>>Doubtful. VFP's internal XML parsing is blazing fast. I'm not sure if they're using MSXML or not internally, but if they are they are low level early binding to it, which will be much faster than anything we can do with the late bound MSXML objects.
>>
>>Internally, XMLTOCURSOR uses MSXML, and CURSORTOXML parses it itself (at least I think it does; haven't actually looked at the code myself). This is would partially explain the speed difference between the two functions.
>
>If it's done manually you always have to worry about keeping up with XML standards - I'm well familiar with this since this is what wwXML does too. But export is considerably easier than import so using MSXML for importing is likely to be a requirement in order to deal with schemas/namespaces etc....
>
>
>+++ Rick ---

Rick,

Do you think the XMLTextReader provided in .Net would be a viable alternative to VFP's XMLTOCURSOR() function which uses MSXML? Here's a link:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguidnf/html/cpconreadingxmldatausingxmlreader.asp

If the writeup is credible, it sounds like it might perform faster for read-only parsing operations.

Great workshop in Dallas last week, by the way! Hope all went well in Milwaukee.