Hello Paul,

p> I know that you're all probably sick of me
p> at this stage, but is there *_any_* way,
p> (kludge, trick, voodoo, sacrificing of virgins)
p> that I can get ISO8859_2 with ISO_HUN to work?
I'm not sure what's your problem: chosen server, chosen admin tool, or
may be their combination? I've tried to do the following, and it has
worked OK:
- run IBExpert (Personal edition is free)
- select Database | Create Database... menu items
- select ISO8859_2 as default character set, and dialect 3
- set appropriate DB registration info for IBExpert (server, DB file,
user name, etc.)
- connect to the created DB
- create test domain:
. Database | New Domain menu items
. name: TEST_DOMAIN
. field type: VARCHAR
. size: 10
. charset: ISO8859_2
. collate: ISO_HUN
. Compile tool button
- create test table:
. Database | New Table menu items
. field name: TEST_FIELD
. domain: TEST_DOMAIN
. Compile tool button

Here is the script:
-----
SET SQL DIALECT 3;
SET NAMES ISO8859_2;

CREATE DATABASE 'C:\Temp\test-hun.fdb'
USER 'SYSDBA' PASSWORD 'masterkey' PAGE_SIZE 8192
DEFAULT CHARACTER SET ISO8859_2;

CREATE DOMAIN TEST_DOMAIN AS
VARCHAR(10) COLLATE ISO_HUN;

CREATE TABLE TEST_TABLE (
TEST_FIELD NEW_DOMAIN
);
-----

As a version of your problem: check if your admin tools use the
correct version of the client library for the chosen server (I mean
gds32.dll or fbclient.dll).

Also you could see all available combinations of character sets and
collations with the query
-----
select cs.rdb$character_set_name, c.* from rdb$character_sets cs
inner join rdb$collations c on
c.rdb$character_set_id = cs.rdb$character_set_id
order by cs.rdb$character_set_name, c.rdb$collation_name
-----


HTH
--
Best regards,
Pavel Menshchikov
http://www.ls-software.com