> Once I had a similar problem using UNICODE_FSS and Firebird .Net Data > Provider 2.1.0 for .NET 2.0. > After lots of testing I found out that the only right solution is to use > UTF8. > One small problem is that IBExpert shows for german umlauts raw UTF8 > characters. But ODBC and Firebird .Net Data Provider 2.1.0 work correctly. IBExpert and ODBC is different question. Our problem is about Firebird .Net Data Provider for .NET 2.0.
> Back than I converted my Database with following procedure. > 1] I created a new DB with UTF8 charset > 2] I copied DB structure into this DB. > 3] I set up two ODBC connection to my old (using charset NONE ) and new > database (using UTF8). > 4] I copied data from old DB into new DB using MSAccess and Ctrl+C/Ctrl+V. > > Pavel In two words you solution was to convert DB from charset NONE to UTF8. In our case with our concrete DB it may take quite a lot of time. We planned this for future but not now. In any cases current handling of UNICODE_FSS and UTF8 looks buggy. ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
