Kbase P110494: The Unicode OpenEdge client fails silently when accessing a file when it's name contains certain Uni
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/17/2010 |
|
Status: Unverified
SYMPTOM(s):
The OpenEdge Unicode client fails silently when reading from a file when it's name contains certain Unicode characters
The OpenEdge Unicode client fails silently when writing to a file when it's name contains certain Unicode characters
Unable to create a file from an OpenEdge Unicode client by using OUTPUT TO when the filename contains certain extended characters
Unable to read a file from an OpenEdge Unicode client by using INPUT FROM when the filename contains certain extended characters
The OpenEdge Unicode client aborts silently
No error messages when the read or write fails
FACT(s) (Environment):
Windows
Progress 9.x
OpenEdge 10.x
OpenEdge Category: Language (4GL/ABL)
CAUSE:
Enhancement Request # 0000003901
CAUSE:
This is a limitation of the product. Like most Windows applications the ABL uses the ANSI functions of the Win32 API to write/read filenames. This includes only the basic character set and does not respect the -cpinternal or -cpstream settings used in the ABL session.
FIX:
You can set which language defines the codepage for using Windows ANSI functions on the Advanced tab of the "Regional and Language Settings" dialog, available through the Control Panel in Windows, however if the characters in the filename fall outside of the ANSI limitations for filenames (Characters 128 - 255) then this is unlikely to be of much help.