>Hi Rick,
>Thank you very much for your reply.
>Yes, UTF-8 works good with databases but not free tables, I have only one idea about it - W2k or VFP cannot convert correctly 866 into 1251 and VFP thinks that it has 1252 (English US code). But it OK, I can use native VFP function for decoding.

I think your choces are UTF-8, UTF-16 or Windows 1252 because that's all that CURSORTOXML can do (not even sure offhand about 1252). What you can do is use no encoding, then encode the content yourself using Windows API calls. But if I remember right the MSXML parser has some problems with some of these types other than majory UTF or ISO types.

>I have another hudge problem - how to write (transfer) datas on the server's disk (typical situation - client have to write something into remote database)? I use function with parameters on server side and parameters are my datas. After receiving this parameters I use standart SQL command INSERT. But the problem is - I cannot transfer russian language - it changes strange - THREE russian letters became the same ONE english letter.

I'm not sure of your environment. If you use plain SOAP messages that should work fine. Cursors and XML passed through may be a problem if it's not encoded properly. I'd approach that problem with just the XML first, then deal with the Web Service after that.

XML Encoding is a very difficult subject to grasp (at least it's been for me) and there's a very detailed KB article in the MSDN knowledge base on it (It was a MSDN article actually). Search for that and that might help you figure out what you need to do exactly.