Hello Carlos, I've been using the UNICODE_FSS character set specification in my connection string successfully when accessing fixed length CHAR(n) columns defined as UTF8.
I have a column with CHAR(32) CHARACTER SET UTF8 specified and when I fill a DataSet through a DataAdapter, I get back my 32 characters without any trouble. However, if I change the UNICODE_FSS in the connection string to UTF8, then I can no longer fill the DataSet, because the length constraint of 32 on my column is not satisfied. Disabling the constraint checking on the DataSet loads a column which now has 128 characters in length, not 32 ! The first 32 chars are correct and then I see 96 spaces. I guess that somehow, there must be some problem with the provider (I'm using a recent version from CVS). Pierre ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
