You should probably verse yourself in SET DATE CENTURY & SET DATE YEAR and the whole process of Date-Windowing and Pivot-Values. When RB gets a date-string w/o the CC component of MM/DD/CCYY - having done Y2K work, I use CCYY although RB uses YYYY in the docs - that is, MM/DD/YY, it uses the SET DATE CENTURY & YEAR to determine how to assign the value for the CC component of the date.
F/Ex: ------------------------------------------------------------ SET DATE SEQUENCE mmddyy // 6-byte edit/input sequence SET DATE FORMAT mm/dd/ccyy // 8-byte presentation format SET DATE YEAR 40 // pivot-year of 40 SET DATE CENTURY 19 // default century value SELECT + MaritalYear, + COUNT(MaritalYear) + FROM + MARITALYEARCOUNT + GROUP BY + MaritalYear ----------------------------------------------------------- This query produced results that showed that individuals who were married (in real life) between 1920 and 1939 were "windowed" into the years between 2020 and 2039 because they were on the "20-side" of the pivot year, meaning that all 6-byte dates with YY-component values GE 40 would have 19 assigned to the CC-component and all LT 40 would be placed in the 21st century. 00 - 39 => 2000 - 2039 --- pivot = 40 40 - 99 => 1940 - 1999 This incident actually happened during Y2K remediation on a large (mainframe) system for a large (Fortune 50 or so) organization. The development/remediation team came to me and I ran this query (in RBase, where I had all the data for the test population) to give them a new and valid pivot date for the system in question. HTH, Steve in Memphis ----- Original Message ----- From: "mjs" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 09, 2002 7:13 AM Subject: A 100 year error > Can anybody give me a clue as to where to look for some kind of bug > in my code that causes the date to advance by 100 years? For some > strange reason, a variable called vdate will get it's value changed > from 09/09/2002 to 09/09/2102. > I do have places in the code where I am changing the date format to > every possible combo looking for user input that might be a date, > like yy, mm/yy, mm/yyyy, yyyy, etc., and then changing it back to > mm/dd/yyyy later. Could this be doing it? > > TIA > Mike > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
