>>Along the same lines I'd vote for better Unicode support especially in the data engine.
>
>Personally I rarely had to deal with unicode related problems. IF so, the STRCONV() function helped me out. Can you point out where UNICODE is a real problem currently

As soon as you need two codepages in the same app. How many times have we told people to use a RTF box whenever they needed some text in a language different from that of the app's? Or, COM strings coming in as Unicode get automatically translated according to the ANSI codepage of the current machine, or not translated at all (after so many years here I've forgotten some of these problems :), or the hoops you have to jump through to send a Unicode string.

Look, even Access is Unicode (at least when it relies on SQL server, haven't tried Jet). I've just opened an app written by a guy who probably wouldn't know Cyrillic from Greek, and added my name in Cyrillic, by just changing my keyboard driver - and it saved it without a hitch. And I was able to see it in Query Analyzer so, also without any setup whatsoever. Wish Fox would do that.