This is probably a character set problem. Full Convert has a character set translator built in, a unique feature. It will auto-detect charset in source and target databases - and translate between them on the fly to preserve your accented characters.

The problem may be happening for several reasons:

• Your source database isn't reporting correct (or at all) character set it is using. In that case, go to Full Convert options, and set source character set used to the right one. Full Convert will do the rest.
• You are using Interbase or Firebird and need to use non-default character set when connecting. Expand advanced section in theInterbase/Firebird connection screen and set it up there.

You can test that we read your accented characters correctly by enabling SQL logging in Full Convert. Go to options and enable 'Display SQL commands sent to target database' option, then rerun the conversion. In the Conversion Summary dialog, you will see a new tab, called 'SQL Log'. Check the insert statements generated to see if we sent correct text to the target. If we did, then the error is on the target database end. For example, in MySQL target which is set up to use latin1 charset, accented character might be lost. Go to our options and change MySQL charset to utf8.