Data Aware Grid Channels - BBj
For this topic's original documentation, see Data Aware Grid Channels.
As of BBj 4.0, data aware grids can manipulate OEM-formatted or Julian dates using INPUTD controls.
Attribute |
Description |
Example |
DATE |
Sets column style to INPUTD, and selects a particular OEM format. If DATE is specified without an OEM code, the date is assumed to be a numeric Julian date. For a list of OEM date codes, see OEM Date Formats. The example program below demonstrates several OEM date formats. OEM date columns should be defined as C(len), where (len) is the defined length of the OEM format. Julian date columns can be specified as any numeric type that is big enough for a 7-digit number. |
"invoice_date:C(3):DATE=AON:" "expiry_date:I(4):DATE:" |
Y2KWINDOW |
When using an OEM date format that is not inherently Y2K-compliant, a Y2KWINDOW must be specified. This shifts the two-digit years forward some number of years from the original implied range of 1900..1999. For example, Y2KWINDOW=30 indicates that the database now assumes a range of 1930..2029. If Y2KWINDOW is not specified, it is assumed to be 0, and valid dates remain in the range 1900..1999. The CITI, SSI, DISC(6) and DISC(8) MM/DD/YY formats must set a Y2KWINDOW that is consistent with the value defined by the application. |
"order_date:C(6):DATE=DISC Y2KWINDOW=50:" |
MASK |
There are three different mask formats, controlled by the following trigger characters in the mask: If the mask contains any '#' characters, numeric masking rules are used and the field is rendered with an INPUTN control. |
order_date:N(7*):MASK=%Mz/%Dz/%Yl: invoice_total:B:MASK=$###,###.00:" customer_code:C(6):MASK=000000:" |
OMASK |
The OMASK attribute is not currently supported with INPUTD fields. |
|
Example
|