Hi,
I am having problems trying to figure out how to use the .Net Provider to call a stored procedure when parameters inside the CommandText contain Umlaute (ä,ü,ö). These chars seem to be replaced by Firebird before the stored procedure is called. I have tried specifiying a charset on the connectionstring, but had no success with NONE, UTF2. I cannot convert the string to WIN1252 (target charset) on either the client side or the server side inside the stored procedure... Using Firebird 2.5 Classic on Windows 7, called from .Net 4.0 Application using .Net Provider Version 2.7.7 Would it help to use SQL-Parameters to avoid this problem? Example CommandText: "execute procedure test 'Zu speichernder Wert mit Umlauten äöü.';" Where the stored procedure does nothing else than storing the passed value inside a table entry. Another application then reads this value as WIN1252. It would be great if anyone had some ideas on this, Ashwani Mehlem ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
