>You know about SYS(987,.T.) in VFP 9, right? It will map ANSI to Unicode and vice versa for SQL Passthrough and remote SQL connections. So as long as you can represent the captured Unicode input as ANSI text you'll be Ok (IOW, if the the character set you're running VFP in can represent the entered characters).
>
>Unicode usage generally only makes sense if you need to display/edit multiple different character sets simultaneously.
>
I am thinking I will try ADO recordset next, as so far all my attempts to save data were fruitless. I downloaded code from your article http://www.west-wind.com/presentations/foxunicode/foxunicode.asp and attempted to run the sample code as is (after changing connection string to point to my test DB).

But somehow I didn't get the result I was supposed to get. The table I got after I ran that code a few times is attached. I only got Russian and Polish once, but nothing else.

I don't know why it didn't work.