At 12:37 PM 1/05/2004 +0000, you wrote:

> > If this is related to your previous Restore problem, then it seems
>likely
> > you have a "rogue" character occupying a column that is a foreign
>key. You
> > could write a stored procedure that loops through the table as a
>cursor,
> > writing the value from the problem column into a variable of the
>correct
> > character set.
>
>Yes, it is related with the previous restore problem.
>
>What do you mean with "rogue" character?
>Do you mean by this a wrong value?

If it is the cause of the transliteration error, it is a value in the
(presumably character-type) FK column, which has been stored with a
character code that is not valid for the character set of the column. See
my other message in this thread for examples of how this can occur. The
important thing is always to have the client connecting with the same
charset as the default database charset. If the target column is a
different character set from the client and database default, then you have
to use the introducer or CAST.

/hb