Laura Stewart wrote: > 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
no that's not going to work. if your stored raw utf-8 in your in database that's what it is, raw utf-8. you can't sort it, full text index it, etc. you really want ucs-2 as that's what sql server (and java/mx/etc.) understand. > 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 unicode hinting applies to inserts/updates & where clauses. > 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. you don't need to. turn on the unicode option for that dsn. boring stuff on that found here: http://www.sustainablegis.com/blog/cfg11n/index.cfm?mode=entry&entry=F9553D86-20ED-7DEE-2A913AFD8651643F ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:197438 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
