Difference: UnicodeCNV_TEXTStmt (15 vs. 16)

Line: 1 to 1

META TOPICPARENT	name="UnicodeTestPlan"

CNV TEXT Statement

Line: 45 to 45

It's not handling Logic fields properly. When CNV TEXT into National/Unicode from Logic the destination field is wrong somehow. It looks ok in the debugger, but if I display it on an image, it shows the field is filled with reverse image diamonds. When comparing via IF to either Y or N, always returns False. * FIXED * Tested with May 23 engine.

Changed:

<
<

Since SET does not work with Group fields and National/Unicode fields, then this probably should not either. It does give compile errors, but the error is "Length of Record Exceeds Maximum Allowed (32k)". Probably should give the same error SET does: "Invalid Storage Type".

>
>

Since SET does not work with Group fields and National/Unicode fields, then this probably should not either. It does give compile errors, but the error is "Length of Record Exceeds Maximum Allowed (32k)". Probably should give the same error SET does: "Invalid Storage Type". * Not a bug * CNV TEXT is allowed to work with group fields contains Unicode/National fields. This error means that the target field isn't large enough.

When converting from Unicode to National, where the Unicode field contains characters not in the National character set, does not throw a transcode error. ** Functions as Designed **
When converting from Unicode to Raw, where the Unicode field contains characters not in the Raw character set, does not throw a transcode error, just silently drops the Unicode character. Should be a transcode error or it should use the substitute character.* FIXED * June 9 engine, Returns F if conversion cannot be performed.
When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field. Same with National to Raw.* FIXED * June 9 engine, Returns F if conversion cannot be performed.