> There are a number of possible causes. CFMX uses Unicode by default, but SQL > Server assumes non-Unicode input. Edit the CF Admin datasource and check the > box under advanced: "Enable Unicode for data sources"
unless the table's string columns' datatypes are "N", thats not going to do anything good. to properly handle unicode w/sql server & mx you should do it end-to-end. use setEncoding, cfcontent, cfprocessingdirective, turn on the unicode option for that dsn and use unicode hints (for instance N'your unicode text goes here.') for all text strings. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
