Kbase 18152: How date fields behave when 1 or 2 digits are used for 4-digit year format.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
GOAL:
How date fields behave when 1 or 2 digits are used for 4-digit year format.
FIX:
In Progress versions earlier than 7.3E and 8.2A, the entering of only one or two digits for a year that has a 4-digit format results in the -yy setting being ignored and the current century used.
For example, if the -yy setting is 1950 and the date format is 99/99/9999, a user in the year 1998 that enters a date of 01/01/00 results in 01/01/1900. The current century is shown as 1900 and -yy is ignored.
This behavior changed beginning with 7.3E (for Version 7 releases) and in 8.2A and later (including Progress 9.0A, etc.).
In these versions, the -yy value is observed and the century value is derived from it.
For instance, in the example above the -yy of 1950 causes Progress to interpret a date entered as 01/01/00 as 01/01/2000 when the format 99/99/9999 was used. Similarly, if you key in 1/1/1, the date 01/01/2001 results.
If you want to know how a particular Progress version behaves in this regard, do the following steps:
1) Start your Progress session with -yy 1950.
(1950 is the default for Progress 7.3E, 8.2A and later, as well as for 6.2N14 on DEC Alpha and VAX OpenVMS, and 7.3C18 on Sequent PTX.)
2) Run this statement in the Procedure Editor:
DISPLAY year(01/01/01).
If you receive 1,901, the version is using the old 4-digit year behavior. If you receive 2,001, it is using the new.
The following versions have the new 4-digit year date behavior. This change is available starting in Progress 7.3E and 8.2A, and has been patched into several other versions (by fixing issue 19970120-024).
You might also wish to visit the patch listings on the Progress website:
www.progress.com//patches/index.htm
NOTE: For a patch version to work, the Progress version must first be upgraded to the corresponding commercial version. Also, if the current patch version for a particular platform is later than the one given below, be assured it includes this fix, since all patches are cumulative.
The patch versions below represent the earliest ones that contain the fix. Also, on these patch versions the default -yy is 1900 and not 1950.
Platform Commercial Version Patch Version
DEC ALPHA OPEN VMS 6.2N05 6.2N14
DEC ALPHA OPEN VMS 7.3C11 7.3C13
DEC VAX OPEN VMS 6.2N05 6.2N14
DEC VAX OPEN VMS 7.3C11 7.3C13
DG/UX 88K 6.3E02 6.3E24
DG/UX 88K 7.3C01 7.3C19
DIGITAL UNIX 6.3C03 6.3C13
DOS 7.3B 7.3B21
HP/UX 8.1A 8.1A04
HP/UX 6.3F01 6.3F17
IBM AIX 8.1A 8.1A05
IBM AIX 6.3F01 6.3F19
MIPS V.4 6.3F04 6.3F11
MS-WINDOWS 8.1A 8.1A04
SCO/UNIX 6.3F01 6.3F12
SCO/UNIX 8.1A 8.1A04
SEQUENT PTX 6.3F02 6.3F07
SEQUENT PTX 7.3C04 7.3C18
SUN SOLARIS 6.3F02 6.3F13
SUN SOLARIS 8.1A 8.1A04
SUN/OS 6.3F01 6.3F05
UNIX V.4 6.3F06 6.3F11
UNIX V.4 8.1A 8.1A04
If your Platform/Version is not represented on this list, you can contact Progress Technical Support to determine if further updates are planned.