-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm not certain that we have non ISO-8859-1 character sets in use,
but we definately use nvarchars without any problems whatsoever. The
entire database is entirely nvarchars for string data, and we're able
to manipulate information out of the DB without any problems at all.
> Your database is handling Double Byte Characters from Asia?
> I find this
> hard to believe.
> CF does not support UNICODE or MBCS. The ISO-8859-1 char set
> can handle
> most Western European languages
> as well as English and default character set in SQL Server
> along with the
> use of nvarchar etc can
> handle any language but CF as I am told by people who work at
> Allaire does
> not support Unicode or MBCS
> in the US Version.
>
>
>> > Because CF can't do unicode, you can't use nvarchar, ntext or
>> > nchar, you must use varchar, char and text.
>>
>> Ummmm.... I don't think so. Our entire site is built on nvarchar
>> fields w/ SQL 7 & CF4.01. No problems of any kind. Non-US form
>> data enters the DB & is displayed on the browser without problem.
>>
>> Best regards,
>> Zac Bedell
>>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
Comment: Please use PGP!!!
iQA/AwUBOWtndwraVoMWBwRBEQKcQQCdHOQCOolW2WFATrk+EowoafyWQTgAoKBE
rhm8ovuIcHjD77XI2Z+xhsWW
=6B0Y
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
