graff, thanks for the comment. If only I could use mysql on this project.... You're right about the "example", which was more obfucsating then helpful, I admit. The way you "tell" MicroSoft SQLserver that data is Unicode is by way of the datatype, strangely enhough. Whereas in mysql any text or (var)char datatype can have e.g. a utf8 COLLATION, in MSSQL you'd use nvarchar (instead of varchar) for storing Unicode data. I am using the so called MSSQL Management Studio Express to actually see the data in the tables. I can paste 'real' Unciode data into it through the interface, as I can run an INSERT-statement with the N'unicodedata' syntax, and it works fine. The problem is somewhere in ODBC/DBD driver, there the fact that the data is to be interpreted as Unicode is lost... Grtz=JPvdV