A customer supplies data to me. A date field is 4 pos numeric (Julian date with only 1st pos representing the year). Problems occur every 10 years. Has anyone encountered this? Any suggestions will be appreciated. Thanks Larry Swain
A customer supplies data to me. A date field is 4 pos numeric (Julian date with only 1st pos representing the year). Problems occur every 10 years. Has anyone encountered this? Any suggestions will be appreciated. Thanks Larry Swain
Larry, what do the 1-digit years mean today (Jan 2001)? When will the problem occur again, and after you fix the problem, what will they mean then?
Using a one-byte year field is common in the automotive industry. You will have to write a conversion program which will append the appropriate decade. From there you can move the field to a date data type. Dave
Yes, I encountered it in 1950 in a punched card insurance system. bobh
of slightly less antiquity, I converted a 'tab' application which had single digit years, but had been modified in 1960 to use the zone field to indicate the decade .. i.e. no zone 5x, A zone 6x, B zone 7x, and AB zone 8x ...