>
>I'm not sure that this is a good idea. The advantage of SAX is consecutive processing, which doesn't require loading of whole document into memory. But it requires a large number of calls while processing, which is slow for IDispatch and late binding. There is an article in MSDN (somethere in periodicals), which demonstrates that SAX may be even slower than XMLDOM in Visual Basic.
>In my opinion the problem of slow processing for a large datasets is in VFP implementation of XMLTOCURSOR, but not in XMLDOM itself. If you can use ADO-compatible XML, then you could try to use ADO persistence in XML format. An example of this conversion you could find in samples for OLEDB library (file #10002). For a large XML files it works at least tens times faster than XMLTOCURSOR.

Actually, I had time to play around with the SAX interface today. It turned out to be MUCH faster. I dropped the 1.5 hour conversion time down to 70 seconds! The number of calls through COM didn't turn out to be that big of a deal. I was really surprised by how well it worked.