>If the problem is the XML encoding in CURSORTOXML, why do you use it then? Why don't you just 'manually' create the XML file? Just create an MSXML object, scan through your original table or cursor, and populate it...
>
>HTH
>Jaime

Sorry for probably my bad English. The problem is in XMLTOCURSOR inside Web Service on the server side. Some times it transforms to correct 1251 code page, some times no... (received XML file is corrected always).