Hi Jorge,

--- Jorge Andrés Brugger <listas@d...> wrote:

> Thanks for your answer. I´ve tried the change with no success ... it´s
> posible that if other users are using the database, the change doesn´t
> apply, even if I get no errors? (Using IB Expert)

I'm only using straightforward ISQL scripts for charset and
collation testing, so I can tell you, it's not a Firebird
problem. Please check with the respective tool author, if using
his tool doesn't produce the same result.

Also I don't understand, which "change" you are referring to,
as the test I've given is about creating a completely new database.

Anyway, if your tool doesn't do it automatically, sprinkling
some COMMITs between your actions may make a difference.

Using again trusty old ISQL, a quick "show table t1" (substitute
your tablename), will reveal whether a column has COLLATE ES_ES.

> And one more question: how can I change all database varchar fields to
> ES_ES collation? (I´ve too much of this ones and all defined as

ISO8859_1)

In actual database or in a DDL script?

For in situ changes in the database there is no official method, but
the better tools will give a workaround, I assume.

In a DDL script, I'd try sed:
s/CHARACTER SET ISO8859_1/CHARACTER SET ISO8859_1 COLLATE ES_ES/g

Regards,
Peter Jacobi