Re: MYSQL doesn't 'see' accents

[Evi Wool]

Hi Peter, I've done some searches in Google so I'm guessing that you mean
Did I give any extra commands when I signed on.
Well I signed on with
Set Names 'utf8';
I then typed in
show variables like "%character%";
which got the results as follows:

| Variable_name | Value |
+--------------------------+----------------
| character_set_client | utf8 |
| character_set_connection | utf8 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | utf8 |
| character_set_server | latin1 |
| character_set_system | utf8 |

Since only one column in the database would contain accents (ironically, the one that contained English words), I modified that column to UTF8

SHOW CREATE TABLE TblEngTest;
and got this enlightening result:
| tblengtest | CREATE TABLE `tblengtest` (
`EngID` int(10) NOT NULL AUTO_INCREMENT,
`English` varchar(255) CHARACTER SET utf8 DEFAULT NULL,
PRIMARY KEY (`EngID`),
UNIQUE KEY `English` (`English`)
) ENGINE=MyISAM AUTO_INCREMENT=37711 DEFAULT CHARSET=latin1 |

I also tried signing in using 2 lines after the usual
cd \mysql\bin
mysql -u root

that is
Set names 'utf8';
set character set utf8;
but the second line seemed to undo the first one somehow and
SHOW VARIABLES indicated that the
character_set_connection was now back to Latin1

I suspect, after all that, the answer is that the database needed to have been created with UTF8.
I've got a horrible problem that while this will (or possibly only MAY) solve one problem, it may create others but I'm not sure about that. If that is so, I'd be better finding the problem rows in Access and then editing manually.