What kind of chars are you trying to store ? What encoding are you using ? Any test page available ?
Laurent
Laurent Fontaine
Sr Web Developer
American Power Conversion
Level 13, 65 Berry Street
North Sydney, NSW 2060
AUSTRALIA
tel: +61 2 8923 9339
@: [EMAIL PROTECTED]
"James Silva" <[EMAIL PROTECTED]>
Sent by: To: "CFAussie Mailing
List" <[EMAIL PROTECTED]>
[EMAIL PROTECTED] cc:
emon.com.au Subject: [cfaussie] Re: MX
encoding issue
25/07/2003 04:14 PM
Please respond to "CFAussie
Mailing List"
> Yes sure, sorry.
> try to use this type of string in the advance option of your dsn
>
> useUnicode=true&characterEncoding=windows-1252
Laurent, didn't work.
Although, it did change the output of the double byte charaters to
different
double byte characters... if that makes sense.
I tried changing the enocoding to UTF-8 (although i told MySQL doesnt
support
UTF-8?)... similar problem, characters are still there, just different.
Any other suggestions?
_______________________
James Silva
Web Production
Gruden Pty Ltd
Tel: +61 02 9956 6388
Fax: +61 02 9956 8433
Email: [EMAIL PROTECTED]
Web: www.gruden.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/
---
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/
