>> P.S. BTW, I'm pretty sure when you have correct unicode database and >> specify correct non-unicode charset when connecting in IBExpert or ODBC >> driver, you will get your characters back. > > This depends on characters. If you have UTF8 column and there's a > japanese character in row, then using WIN1250 will not get right > result - obviously, 'cause WIN1250 has no idea about japanese chars.
Are you willing to tell me that with NONE charset you can see Japaneese, Chinese, Czech and Ukrainian characters simultaneously? :)) Roman ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
