Hello,

I can't figure out the following malformed string scenario with Firebird
2.5.

A customer is running a trace session on a Firebird 2.5 database using
NONE as character set. Received trace data e.g. can contain characters
like 'Ø'. When trying to store the trace data in another UTF8 database,
I get a malformed string exception. The process which stores trace data
is connecting with UTF8 to the UTF8 database.

Any ideas?

Thanks.

--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/