thousandsChar

Valid in all scopes

(local scope invalid when staticNumericChars=true)

The value of this configuration variable tells Tango Server what character is used as the thousands separator in numbers. For example, in the US, the comma (",") is normally used for this purpose. Only a single character may be assigned to thousandsChar. If a longer value is assigned to it, only the first character is used. The value also should not be the same one specified for the decimalChar configuration variable, as this would create confusion when numbers were specified.

Tango Server uses this value in order to properly evaluate numbers in conditional comparisons (for example, Branch action, <@IF>, <@IFEQUAL> and <@ISNUM> meta tags) and in calculations performed with the <@CALC> meta tag.

The setting is also used when Tango Server is constructing SQL for Search, Insert, Update, and Delete actions. Tango automatically removes the character specified by thousandsChar from any values specified for numeric columns. Use the <@DSNUM> meta tag to perform the same function on numbers you specify in Direct DBMS actions.

The default value of thousandsChar is "," (a comma).

thousandsChar and Scope

For more information, see "staticNumericChars".

When staticNumericChars has the value TRUE (the default), changing the value of thousandsChar has no effect during the execution of an application file. Changes to thousandsChar in user, domain, or system scope take effect with the next application file execution; as a consequence, changes to thousandsChar in local scope have no effect.

See "Understanding Scope" in Chapter 7 of the User's Guide.

When staticNumericChars has the value FALSE, thousandsChar works with scope in the standard way.

See Also

currencyChar
DBDecimalChar
decimalChar
<@DSDATE>, <@DSTIME>, <@DSTIMESTAMP>
<@DSNUM>
staticNumericChars