are unicode columns (nvarchar - ntext).
-mark
-----Original Message-----
From: Mark Drew [mailto:[EMAIL PROTECTED]
Sent: Friday, June 11, 2004 8:28 AM
To: CF-Talk
Subject: Re: Character encoding - CFMX and SQL
you have to create the columns in MS SQL as nVarchar so that they can
cope with international chraracters...
Regards
On Fri, 11 Jun 2004 08:22:31 -0500, Mark A. Kruger - CFG
<[EMAIL PROTECTED]> wrote:
>
> Folks,
>
> I have an international customer who was running on Access and we moved from cfmx 6.0 to cfmx 6.1 and from access to
> MsSQL 2000. Prior to the move when he updated a table on access it worked fine. After the move when he updates and
uses
> language specific characters (Italian) it changes the characters to a question mark in the DB. Note, the "old" data
in
> the db is stored and displayed correctly (wiht the right characters)
>
> For example:
>
> Nel cominciare l'analisi
>
> In the old data this phrase is stored correctly, but when it is inserted (using a form and CF template) now it ends
up
> in the database like this:
>
> Nel cominciare l?analisi
>
> In the application.cfm page we have the following directive:
>
> <cfprocessingDirective pageencoding="ISO-8859-1">
>
> <cfset setEncoding("form","ISO-8859-1")>
>
> <cfset setEncoding("url","ISO-8859-1")>
>
> <cfcontent type="text/html; charset=ISO-8859-1">
>
> Any one have any helpful hints?
>
> -Mark
>
> Mark A. Kruger, MCSE, CFG
> www.cfwebtools.com
> www.necfug.com
> http://blog.mxconsulting.com
> ...what the web can be!
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
