Hi Chris, I recently had the same issue -- upgraded to CFMX 6.1 with SQL Server 2000 and our Greek and Lithuanian affiliates' content went kerplooey.
After many hours of searching I found my answer buried in one of Ben Forta's reference books. Here's a link to a Macromedia TechNote. http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_18331. Assuming your problem is the same as mine was -- and it looks and sounds exactly the same -- your page encoding is fine (UTF-8 was probably sufficient). It's the database queries that need attention. As laid out in the TechNote, SQL Server 2000 needs to receive an N prefix before the quoted string to recognize it as Unicode. Otherwise it converts it to the server's own codepage and renders any character not in the "local" character set into garbage. Here's the tricky part I ran into. The Unicode prefix ( N'asdf') isn't compatible with CFQUERYPARAM as far as I can tell. I resorted to stored procedures for every instance because I was *very* uncomfortable with losing CFQUERYPARAM. I hope this helps you. And if it does, I'm very glad that someone else can benefit from the hours I spent pulling my hair out over this... :-) Laura Stewart ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:197436 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
