>>Not sure why you wouldn't want to allow 4 digit years. User's can still just enter the last two if it's 19xx. I know form real estate is can be a problem, but, maybe it's just because I've always done a lot of government related apps, but my users have been having to enter 2k dates since the 80's.
>Nancy,
>
>My apps have been using four digit years since the early 80's and they will continue to use four digit years forever. I ahve alot of reasons for doing it this way, not the least of which is demonstrated by my asking the thread what date is this 02/12/50? There is not one person who can answer that question. No user can asnwer that question when they see that date on screen or in a report either. They have to "ASSUME" something about the year. They may assume correctly or they may assume incorrectly, either way they cannot KNOW what the date is.
>
>I had to develop systems that dealt with three centuries, 1800, 1900, and 2000 and with that requirement there was no way of using any trick to fool people into thinking that the year has only two digits.
>
>However, with all of that said, there are alot of developers who want a solution to using two digit years with the next millenium comming up and I think they should get the best info that I can give them. I gave up on trying to educate them into the fatc that the year 1998 and not 98 :-)

There is one disadvantage by using 4 digit year. After type the month, the cursor comes to the year field and the user has to press Right arrow key twice to come to the last two digits of the year. In some applications that I have developed, is data is randomly entered for a period of 2 years. i.e 97 sometimes and 98 sometimes. There are other work arounds, but one has to get used to typing them in some order. Was there any resistance to entering 4 digit year from the users, initially ?

Rakesh