> I have upgraded from 2.1 to 2.5 today and have noticed a different
> handling of special german character (ä,ö, ü etc.)

> If a trigger contains these characters in comments or assignment of
> values it cannot be saved.

> cTEXT = 'Baustelle wird überprüft';
> /* Alle Felder werden auf Änderungen ueberprueft */

> [...]

> Question: is this related to the character setting of the DB?

> DEFAULT CHARACTER SET NONE;

It is. NONE is a character set that just stores values as they come
in. It doesn't care about their "meaning".

Your access tool very probably uses another character set than NONE,
probably WIN1252 or ISO8859_1. There is nothing to match the "German"
characters (all characters with a Unicode scalar value larger than
127) to NONE. So it is correct for the Firebird client to fail.

What can you do? You can search for a setting in your tool that allows
you to set the client connection character set (that must be in the
settings where you also define the database name, user name and
password).

If you have power over the database structure you should upgrade your
string fields ASAP to a real character set like ISO8859_1 or WIN1252
or, to have maximum flexibility, to UTF8 (which is Unicode). Firebird
can match all character sets between each other, "NONE" is one of the
rare exceptions.

Use "NONE" only, when you are 150 % sure that you will only store
English text or no human language text at all in your database ...

Best Regards

Stefan



--
Stefan Heymann, Tübingen, Germany