Hello,

I already have the Charset=UNICODE_FSS; set in the connection string
and an equivalent connection string actually did work previously in
the previous database version and also the inserts that were put to
database correctly were done with the same connection string. But
maybe I try to change the connection string somehow...

BR,
MariJo

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> At 10:53 AM 30/09/2004 +0100, you wrote:
> >Hello,
> >
> >I have a problem with unicode characters äåö etc that appeared

after I

> >changed from 1.0.3 database version to database version 1.5.1 and

newer

> >.net provider.The problem is that when I insert data (strings)

with isql

> >script and I have the setting SET NAMES UNICODE_FSS before the

connection

> >phrase. (I have written the script in windows notepad)
> >
> >The data seems to be OK when I look at it with IBSQL and that

program

> >shows the problematic characters allright. But when I query them

with .net

> >provider for firebird then all the problematic characters are left

out

> >from the .net dataset.
> >
> >But when I use this same .net provider to insert this data as

unicode then

> >this provider can get the datas without missing any ä:s and ö:s.

And that

> >is why it seems that there could be something this isql script is

putting

> >is not OK.
> >
> >Would be really really grateful if anyone could help me with this

one. It

> >is odd that everything was working just great before I upgraded to

the

> >newer versions of database and provider.
>
> It's most likely that your problem comes from not correctly setting

the

> database connection parameter to the correct character set. This

is the

> API equivalent of using SET NAMES in isql.
>
> Ask for help on the .net provider list. Hint: you are probably

looking for

> a connection parameter with a name like "charset" or "lc_ctype".
>
> ./heLen