>>Hi Paul,
>>
>>XMLTOCURSOR() internally uses XMLDOM( MS XML 3) which isn't design for processing large XML sets. You may try SAX (Simple API for XML) which generally better suited for extremely large XML documents. The code by Doug Hennig from Re: Can I use SAX in VFP? Thread #613336 Message #613392 may help you started.
>>
>
>Interesting idea. Thanks for the link.

Paul,

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.