Toby Tremayne wrote: > ok I've tried this again and have some interesting results. I used > pgAdmin's migration tool to try to move the data across - I created > the pg database as unicode, and used the unicode option for the > migration - and ended up with an error: > > An error occured at: 29/01/2003 11:11:54 AM: > -2147467259: ERROR: Invalid UNICODE character sequence found (0xee7472)
That is the typical error when inserting high ASCII in a PostgreSQL database. > Any ideas? I can only assume that either there's some weird character > gone in through a copy and paste from msword to the website textbox > used for input, as Paul suggested, or CF4/5 has saved bad unicode in > there and now I'm stuck with it. how does one go about correcting > something like this? There is the hard way. You need to extract the data from the database using CF 4.5, then cfhttp it to CF MX, use setEncoding() to fix the charset there and then insert it into the database. And there is the uncertain way. It should be possible to import the data correctly in some PostgreSQL database with encoding ISO-xxx. Then you should be able to use the built-in Convert() function to convert to unicode, which would eliminate the cfhttp step. Haven't tried that though. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
