Paradox 4.x: FPUAWARE needed for ISBLANK function to work

[gbl]

vDos Version 2022.05.01 introduced a new Config.txt directive: FPUAWARE = 0-3 (0 = None, 1 = Present + conditional rounding (default), 2 = Rounding off, 3 = Rounding on.

Without this directive, my PARADOX PAL scripts stopped working properly - function ISBLANK did no longer distinguish between BLANK and *ZERO (with Blank=Zero option on)

With Jos' help, I was able to get ISBLANK function to again distinguish between BLANKS and ZERO by setting FPUAWARE to 0 or 2. Default of 1 or 3 caused ISBLANK function to misbehave.

From PAL User Reference Guide:

Blank Values
---------------
In Paradox, the value of any field in which no data is present is blank, or null.
The value of any PAL expression (except those that evaluate to type logical) can also
be blank.
A blank string value is denoted by the empty string ("") and not a space (Asci
32). Blank numbers and dates can be generated by the BLANKNUM and
BLANKDATE functions respectively. You can use the ISBLANK function to test
whether the value of an expression is blank.
If you want to indicate a value of 0 in a numeric field of a Paradox table, it 1s al-
ways preferable to explicitly enter the value rather than to leave the field blank.
There is a special Blank=Zero option in the Paradox Custom Configuration
Program that you can use to treat blanks as zeros in calculations. Unless this option
has been enabled, any PAL calculations involving blank numeric values will result m
a script error. You can use the ISBLANKZERO function to check on the current
settings.

Gernot