Feeling a bit "NumToCharred"...

[Mark Wieder]

Richmond-

Friday, December 18, 2009, 11:16:47 AM, you wrote:

> useUnicode throws a tantrum with "&&", as it does with " ", so
> everything (which is incredibly tedious) has to be down the
> numToChar way (i.e. no mixt forms):

> on mouseEnter
>     set the useunicode to true
>     set the unicodeText of fld "GUFF" to numToChar(7749) & numToChar(32)
> & numToChar(43)
> end mouseEnter

You should report this as a bug. The doc comments for setting the
unicodeText of a field state that any non-Unicode chars are converted
to single-byte chars to save storage, and this is obviously not
happening.

-- 
-Mark Wieder
 mwieder at ahsoftware.net