|
| Inicio → WINDEV 2024 → [WD19] Problem when storing Binary Memo with non-lLatin characters |
| [WD19] Problem when storing Binary Memo with non-lLatin characters |
| Iniciado por guest, 21,abr. 2015 09:33 - 3 respuestas |
| |
| | | |
|
| |
| Publicado el 21,abril 2015 - 09:33 |
Hi all.
I have a problem when try to store file inside a Binary Memo field, when this file has non-Latin characters (Greek).
The stored path name becomes: ??????????S ???. ????G??????S.docx, and I can't extract it later, in order to open it.
Any advice please?
Best Regards
Vassilis Boutsikas |
| |
| |
| | | |
|
| | |
| |
| Publicado el 21,abril 2015 - 10:42 |
Hi Vasillis,
Not sure if this helps but is your current configuration set to unicode?
Since some years all my projects are fully unicode working even on Korean and Chinese locations of my customers with their local double-byte character sets. Works like a charm.
There's an option in the analysis editor to modify all string field definitions to unicode in one go...
Best regards,
Peter H. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 21,abril 2015 - 12:39 |
Dear Peter,
The Project (Code + Analysis) is in Unicode format. I use it since WD17.
The problem caused by HLinkMemo function For some reason, it doesn't translate propelry the Greek characters (and possibly other non-Latin).
Thank you for the try.
Regards... Vassilis |
| |
| |
| | | |
|
| | |
| |
| Publicado el 21,abril 2015 - 13:28 |
Hi Vassilis,
if you can reproduce the problem in a small project and send it to pcsoft, it's probably the safest long term solution
As a work around, you could try to :
- use fshortpath or the file inside the hlinkmemo
- and if that works, store the "real" name of the file as extended information in the hlinkmemo (maybe with a unicode to ansi, if that is a problem too)
Best regards |
| |
| |
| | | |
|
| | | | |
| | |
|