OOPS ! Change the FORMAT to mm/dd/yyyy Leave seq mmddyy
Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: Tuesday, May 10, 2011 5:13 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: A 2-digit, 4-digit date problem Karen, I had to change the sequent to yyyy in 7.6 I frequently got weird results without that change Why not make the threshold year 21? Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, May 10, 2011 4:41 PM To: RBASE-L Mailing List Subject: [RBASE-L] - A 2-digit, 4-digit date problem Using 7.6, bringing pieces of a 6.5 windows app over. Table has a column issue_date. There is a rule on the column that the date cannot be > .#DATE My date settings are: date format mm/dd/yy date sequence mmddyy threshold year 88 century 19 In 6.5, if they wanted to type in a date of 1/1/1967, they could type it in the form with the full 4 digits, it would save properly, and would not violate the rule. If they had typed in 1/1/67 by itself, it would violate the rule because it would think it was 2067. In 7.6, if you type in the 4-digit year, the first 2 digits disappear when you leave the field, so you just see the "67". And apparently it is evaluated as 2067 and violates the rule. There appears to be no way to type in 1967 if you have the sequence mmddyy. Is that true?? I really don't want to change the sequence to mmddyyyy because 99% of the time they will be typing in the year 2011. This application is very heavy into dates, and this is the first form I'm converting. It's disheartening to have this problem right off the bat! I'm hoping someone has a workaround for me? Thanks! Karen
