I just tried this with LV2015 (no SP1) and have no problems with it.
I used these settings:
I set "coerce" for minimum and increment = 1, as these are completely making sense for an U64 value. (But also "ignore" for minimum and increment does work fine.)
When I input a value bigger than 1E19 the U64 coerces (as expected) to 1E19…
You can always input "1e19" instead of a 1 followed by 19 zeros. No need to count zeros or keystrokes…
The most recent datatypes (EXT and 64-bit integers) suffer from these types of issues. The coerce and limit logic uses DBL and 1E19 is not representable as a DBL, so the value 10....01024 is not distinguishable from 10....00000.
then why does my U64 control coerce inputs nicely to 1e19 - even when I input 1e19+1 ("100…01")?