>>>Not according to Christof Lange.
>>>
>>>Which one of you two are right??
>>>
>>>Joe
>>
>>Sylvain is correct, it acts the same in 5.0 and 6.0. It is related to the Y2K compliance. The suefullness of the rollover is that it allows the user to type two digit years and adjusts the cenury accordingly.
>
>See my other post. When a TextBox is showing 4 digits, typing 2 does not work.
>
>
>>
>>IMO, any developer that creates a system today that shows ambigous dates deserves to be sued for it. With all the discussion hat Y2K is getting there is no excuse for allowing your users to shoot themselves in the foot. We are experts in this area and the users are not, on some issues we need to tell them how it must be.
>
>Jim, nobody is going to shoot themselves in the foot. I work here and understand the requirements. I understand fully that some issues need to be argued strongly. I have argued some of those issues. You aren't here and don't know the situation as I know the situation.
>
>>
>>On most issues the users can decide what they want, but would you allow them to delete a customer record and leave orphaned invoices lying around? Do you allow them to haphazardly change primary key values on their data?
>
>We never delete a client record. A flag is set and the change is recorded. If a user deleted a client on 99/04/01 and lated pulled-up an invoice dated 99/03/01, the invoice would pull the client information that was in effect on 99/03/01. But I understand what you are saying. I have understood this for a long time. I just don't feel the need to argue the 4 vs. 2 digit year issue. And I don't own the company. I don't have the final say even if I did argue the point. I have a strong influence, but sometimes that isn't enough. This is not a black and white problem. Can you argue that typing 4 digits is as fast as typing 2 digits? No. Therefore there is a benefit to typing 2 digits. Now, the decision process involves weighing the different benefits/problems. Given just one benefit for 2 digits (speed), one can decide that it is a better choice depending on how he weighs this benefit.

2 or 4 digits on screen are not so critical as long as data integrity supported. It's not a big deal to utilize Textbox.Century property and have 4-digits for some wider (or occasional) range dates and 2-digits for dates rigidly controlled by ROLLOVER clause.