Dna Ut 14. Jún 2005 22:57 Paun napisal: > If you use MyODBC driver this is because MyODBC driver have no full Unicode > compatibility. > > You must avoid it, and yse MySQL connector/Java driver. It's working OK, at > least in serbian :) > Many people who use MyODBC have the same problem, and as I read in > e-forums, there will be ok in new version of MyODBC driver. > I can try Java driver but it has to be set up for cp1250 char set and I am not sure how to do it. But I am not sure if this is the problem. OOo displays my fields correctly so there is maybe something with interpretation of char set when I change char set in MySQL.
My problem is that when MySQL fields are declared as latin1 char set I can write into them characters from other char sets (in my databases windows-cp1250) and OOo displays them correctly. But in select commands I get wrong collation. And when I change in MySQL char set property to cp1250 then OOo displays characters wrong. juraj --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
