In this section: |
To apply the sliding window technique correctly, you need to understand the difference between a date format (formerly called a smart date) and a legacy date:
For details on date fields, see the Describing Data manual.
Reference: |
The rest of this topic refers simply to DEFCENT when either DEFCENT or FDEFCENT applies, and to YRTHRESH when either YRTHRESH or FYRTHRESH applies.
Supply settings for DEFCENT and YRTHRESH in the following cases:
On input, the function will use the window defined for an 16 legacy date field (with edit options). The output format may be 18 (again, with edit options), which includes a 4-digit year.
For example, you can use the sliding window technique in applications that use FIXFORM or CRTFORM with MODFIY.
Follow these rules when implementing the sliding window technique:
Finally, keep in mind that the sliding window technique does not change the way existing data is stored. Rather, it accurately interprets data during application processing.
The following results occur when you use the sliding window technique with a MODIFY request or FOCCOMP procedure:
Date formats are validated on input. For example, 11/99/1999 is rejected as input to a date field formatted as MDYY, because 99 is not a valid day. Information Builders generates an error message.
Legacy dates are not validated. The date 11991999, described with the format A8MDYY, is accepted, even though it, too, contains the invalid day 99.
|
Information Builders |