I also tried the Firebird ODBC with no luck. I set up the ODBC data source to use the WIN1252 charset and then I connect to the ODBC datasource from my application.
I still get this error: >> ERROR [HY000] [ODBC Firebird Driver][Firebird]arithmetic exception, numeric >> overflow, or string truncation Cannot transliterate character between character sets >> ERROR [HY000] [ODBC Firebird Driver][Firebird]arithmetic exception, numeric >> overflow, or string truncation Cannot transliterate character between character sets -----Original Message----- From: Louis van Alphen [mailto:lo...@nucleo.co.za] Sent: 08 January 2010 12:00 PM To: 'firebird-net-provider@lists.sourceforge.net' Subject: RE: [Firebird-net-provider] Character set problem between with Firebird & .NET provider I tried WIN1252 but it still does not work. I did the following steps: 1. Exported all metadata and data from the database 2. Created an empty database with WIN1252 char set 3. Imported all metadata and data 4. Set the charset on the /NET provider to WIN1252 I still get the transliteration error when accessing certain data -----Original Message----- From: André Knappstein, Controlling [mailto:knappst...@beta-eigenheim.de] Sent: 07 January 2010 04:21 PM To: Louis van Alphen Subject: Re: [Firebird-net-provider] Character set problem between with Firebird & .NET provider I would second what Jiri wrote. We have been using 8859_1 widely. This works okay with ODBC. Using .net, some things did not work correctly. Or rather they worked correctly but not as we expected :) ISO8859_1 does - for example - not really specify a solution for displaying the Euro symbol (€). We changed everything to Win1252 instead, which supports spanish and french characters as well as German Umlauts and ß ciao, André -- ~~~Ihre Nachricht~~~ LvA> Hi, I would appreciate it if someone could help. LvA> LvA> I am I South Africa and is developing an application for use in South LvA> Africa, France and Italy. Therefore the application and database has to LvA> support the French and Italian special characters. LvA> LvA> I created the database using IBExpert with a default character set as shown LvA> below LvA> LvA> SET NAMES ISO8859_1; LvA> CREATE DATABASE LvA> 'D:\Projects\Intertrade\Tech\Database\FRANCECROCO V26.FDB' LvA> USER 'SYSDBA' PASSWORD 'masterkey' LvA> PAGE_SIZE 8192 LvA> DEFAULT CHARACTER SET ISO8859_1; LvA> LvA> So I am assuming that all text type fields will default to this character LvA> set. LvA> LvA> My application is developed in .NET 2 VS2005 and am using .NET client 2.0.1 LvA> LvA> My application sets the character set to ISO8859_1 when connecting to the LvA> database. When I connect to the database and want to access some data that LvA> the customer has updated, I get the transliteration error. Data that the LvA> customer has not touched i.e. does not contain special characters shows ok. LvA> LvA> What else do I need to do? LvA> LvA> Thanks LvA> Louis ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
