Pham Huu Le Quoc Phuc wrote: > Anybody fall into this problem. Please help me.
It's only been a few hours, have patience. Many people on this list will be asleep at the moment. In the meantime, I would suggest you try to provide some more information about the problem you're seeing. As a quick guess, I'd say this is something to raise on the .net provider list, but you'll need to include some more information first. For example: 1. What does the stored procedure code look like? 2. What does your C# code that is catching the exception look like? 3. What does the message display as when it works (from SuperServer) 4. What does the message display as when it does not work (from Embedded) UTF-8 *is* unicode, so your assertion that "UNICODE" and "UTF-8" are somehow different does not make sense. UTF-8 is one method of encoding unicode and I'm assuming when you say "UNICODE" you actually mean UTF-16. Additionally, string in .NET are opaque data structures -- there is no such thing as a "UTF-8 string" or a "UTF-16 string" in C#. Dean. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
