Thanks Mark.
We have managed to resolve the issue - it's apparent that a lot of other people have experienced the same problem. In the off chance someone else runs into this, the following threads shed some light:
Thanks,
Sarah.
-----Original Message-----
From: Mark Lynch [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 7 January 2003 1:05 PM
To: CFAussie Mailing List
Subject: [cfaussie] Re: CFMX - special characters
Hi Sarah,
I've just had a look on the MYSQL Website
http://www.mysql.com/products/mysql/ and under the upcoming features -
Character set handling, with full Unicode support. It seem's to me that
MySQL doesn't currently support unicode properly.
You may be able to specify that the db use UTF8 as a codepage - just and
idea not sure if it is possible (haven't used mysql enough).
The testing you have done does not seem to be thorough enough to narrow it
down to the ODBC (or should be JDBC) driver. This is because CFMX is
Unicode and CF5 is not while MSSQL2000 is Unicode compatible and as
mentioned above I do not think mySql is.
When I was working on this I set up a test page which submitted the data
to the database in both an varchar field and an nvarchar and displayed the
results on the page as well as the actual form data that I had just sent -
in order to compare the results. The ASC() function is very useful for
this.
Another thing to try playing around with the various CF functions for
conversions such as HTMLEditFormat(), HTMLCodeFormat() when you are
displaying the page.
Hope some of that helps.
Mark
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
>
> ------_=_NextPart_001_01C2B5E3.6D461BB0
> Content-Type: text/plain
>
>
> Thanks for your replies Mark and Grant.
>
> After a bit more poking around, we are beginning to think that it is in fact
> the MySQL ODBC driver that comes with CFMX which is causing the problem, and
> not supporting the Unicode.
>
> When using the exact same code with a combo of CFMX and MS SQL 2000 the
> problem does not arise. However CFMX and MySQL results in problems. Meaning
> ...
>
> - CFMX is not the problem - as it works fine with MS SQL 2000
> - MySQL is not the problem - as it works fine with CF5
>
> ... leaving the ODBC driver.
>
> Does this sound like a possible cause? Or should we tackle it from the angle
> you have outlined Mark?
>
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
---You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
