Kbase 20294: ADM2 - Don't Save Source Files with the TTY Procedure Editor
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
Appbuilder
ADM2
Smartobject source file corrupted
Source file still compiles
When the SmartObject is run the strings are not delimited in the manner that the ADM2 expects and strange runtime errors happen.
Unexpected runtime errors after saving ADM2 smartobject file on the TTY
CAUSE:
SmartObject (ADM2) source files generated by the AppBuilder contain string constants that have chr(1), chr(3) and chr(4) characters embedded into the string.
Because of this, these source files should not be opened by the TTY Procedure Editor (the Procedure Editor on UNIX machines).
Opening the file in the TTY Procedure Editor causes these characters to be replaced by blanks because the TTY Procedure Editor does not consider these "unprintable" characters to be valid within a source file (because you cannot enter them from the keyboard on UNIX). If you then save the source file, it is now corrupt from an ADM2 perspective.
FIX:
Save SmartObject source files using the Appbuilder and not the TTY Procedure Editor