A Business Objects 4.1-based application was tested for ‘correct’ 2-digit year value to 4-digit year value conversion (i.e. Y2K Windowing Logic with a pivot year) under a Y2K testing effort. The BO 4.1 Reports module behavior does not inform the user as to the exact date conversion that is performed – i.e. 2-digit year values between 00 and 29 are converted to values between 2000 and 2029, and 2-digit year values between 30 and 99 are converted to values between 1930 and 1999. This has resulted in confusing (and unsuccessful) reporting results when a reporting range end date beyond the year ‘30’ (i.e. ‘2030’) is entered (End-dates have their year values converted to values between 1930 and 1999). This behavior fails established criteria for proper user prompting associated with Y2K-impacted date values.
The current ‘owners’ of this application are seeking ideas for a solution to this problem. The hope is that someone in the BO user community has wrestled with this same problem and come up with a ‘date mask code segment’ fix that echoes to the user the explicit 2-digit-year-to-4-digit year date conversion and prompts the user to enter the full 4-digit year value. Any ideas or code examples would be greatly appreciated. Thanks.
Robert Wallace
Y2K Tester @ AT&T U.S. Phone: 336-279-2452 rwallace@ems.att.com
Listserv Archives (BOB member since 2002-06-25)