>>Thanks for that Jim.
>>The sad bit is that if you're converting a 2.6 app just because you want Y2K you've got to rewrite the screens anyway. Dang!
>>So, in effect 'set century off' doesn't work anymore. I've noticed grids/browses are strange too.
>>I think I'll just go with the flow and force the users to enter the extra two digits.
>>
>David,
>
>First, as you have already seen displaying four digit years does NOT require users to type four digits, it only display all four digits. The only issue with four digit years is that editing and existing date requires that the user make sure they change the last two digits and not the first two.
>
>Also the four digit display of dates after the 2000 using ROLLOVER is by design. It is intended to remove any abmiguity from the user.
>
>Every time this discussion come up I ask the following question, what date is 12/13/01?
>
>If you said 2001 you are wrong, it is 1501. The point is that the only way to remove ambigous dates is to show them as non-ambigous dates (that is all four digits of the year).

Well years aren't limited to 4 digits. What about 10201? It's a long way off but it will happen. The Y10K bug. Of course I'm taking this a little tooooo far :-)
Also, if a date text box already has a date in it the user has to enter the four digits, or do some fancy fingerwork.

It really means though that SET CENTURY OFF is pretty much useless now. I've already changed my base class environment to "ON" and I'll run with 4 digits.