SET TEMP from a literal does not recognize \uxxxx or \UXXXXXXXX character sequences * FIXED * tested with May 23 engine
Does not throw transcode errors when setting unicode characters into a national field. ** Not a bug FAD**
Stops moving characters when it hits a unicode in the from field and the to field is a raw type. Just ignores remaining characters. * FIXED * tested with May 23 engine.
Changed:
< <
When SET TEMP from a literal containing \uxxxx or \UXXXXXXXX, if you use a start position or length other than 1, you get incorrect results in the destination field.
> >
When SET TEMP from a literal containing \uxxxx or \UXXXXXXXX, if you use a start position or length other than 1, you get incorrect results in the destination field.* FIXED * tested with June 9 engine.
-- SteveFrizzell - 2011-03-08
\ No newline at end of file