Sergey, Hi. What is SAX? Is it a library, or a third party tool?
I find XML to be very slow if there is a large chunk of data. XMLTOCURSOR works OK for small datasets, but on a large file it is like watching grass grow.

I had to create some data imports via XML. I tried XMLTOCURSOR and timed it. It ran for two hours and was not done, and there was no way of telling how much longer it would be. Then I wrote a parsing program using low level routines [FOPEN(), FGETS()]. The same amount of data takes six minutes to import in this manor. We're talking about more than a quarter million records, even though the record length isn't that long. I forget how, but I had estimated that the XMLTOCURSOR() route would have taken upwards of five hours. Let's see...five hours, six minute...five hours, six minutes...three times a day. FOPEN() wins!

Dana

>>This works fine, but if there are a lot of records to read in, I would like to generate a progress window. SET NOTIFY does not seem to have any effect with 4000 records. Any ideas?
>>
>>XMLTOCURSOR('C:\profiler\dataxfr\ER009999.xml','tempxml',512)
>
>There's no buil-in progress bar. The best you can do is to show some AVI to the user. If you want control over provcessing, consider using XMLDOM. If, in addition, you need sped, look into using SAX.