|
<< Click to Display Table of Contents >> Navigation: Telegram > 2020 > 08 > 05 > Telegram_2020-08-05T16 |
2020-08-05T16:12:26
I've seen this many times. This happens because the DB layer is trying to translate a Unicode char into another charset (the one that you have in your DB) and it fails.
Check the field type of your table and also the charset used in the DB. The problem is there
2020-08-05T16:25:28
Maybe the code page of the database is another rather than Unicode.
2020-08-05T16:25:44
Or if there is a routine that converts from one encoding into another
2020-08-05T16:25:58
It happens alot with winxxxx code pages
2020-08-05T16:29:07
Yes... Win1252, I think, is the king of these errors
2020-08-05T16:38:39
Yup.
2020-08-05T16:48:42
hi. i send you mail replay.
2020-08-05T16:49:36
Unless there is a legacy issue, or some specific constraint, Unicode should be what you are using. The older language specific encodings will cause you nothing but grief and are intended to be for legacy support only.
2020-08-05T16:49:49
This is in general, not specific to IW or even Delphi.
2020-08-05T16:50:26
Delphi was a bit late to the party for Unicode support, but even with that lateness Unicode has been supported and the default since Delphi 2009.
2020-08-05T16:56:59
Also check any code like TEncoding.UTF8.fromxxxx maybe there can be the error. Because it cannot convert from one code page to UTF8. The best solution as type: mention @Alex7691 said. Try to manage the same code page in this case. Unicode along all the tables and Database itself.