Hi,

I hope someone else will follow up. I can't help any further I'm afraid.

Kjell

Nikolaus Kern skriver:

> Hello Kjell,
>
> I am using EMS SQL Manager and also tried directly on iSQL. Same results
> in both systems.
>
> These comments and assignments are part of a SQL upgrade script. This
> was executed always successful with version 2.1.3-18185.
>
> Niko
>> Nikolaus Kern skriver:
>>> Hello all,
>>>
>>> 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 */
>>>
>>> Both lines fail with the same error msg:
>>>
>>> Unsuccessful metadata update.
>>> MODIFY TRIGGER failed.
>>> Malformed string.
>>>
>>> SQL Code: -607
>>> IB Error Number: 335544351
>>>
>>> Question: is this related to the character setting of the DB?
>>>
>>> DEFAULT CHARACTER SET NONE;
>>>
>>> I can write and read values from the DB that contain the german special
>>> characters without any problems.
>> In the past, for me this kind of problems has been caused by incorrect
>> unicode handling in client software. So, what client software are you
>> using? It seems to be geared towards InterBase, considering "IB Error
>> Number"...
>>
>> Kjell

--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64