Difference: UnicodeCNV_TEXTStmt (3 vs. 4)

Line: 1 to 1

META TOPICPARENT	name="UnicodeTestPlan"

CNV TEXT Statement

Line: 46 to 46

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
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".

Changed:

<
<

>
>

when converting from Unicode to National, where the Unicode field contains characters not in the National character set, does not throw a transcode error. It should.
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.
When converting a Unicode field containing a spiky ball (0xA4), I get a Euro symbol in my Raw field.

-- PeteBrower - 2011-03-17