>>>>>>Hiya Ken:
>>>>>>
>>>>>>Sheesh. What a bozo lawsuit.....hey, I volunteer to be a witness for the defense :-)
>>>>>>
>>>>>>>VFP is the focus of one of the first suits against Microsoft over the Y2K bug. Seattle Times Reports: Developer Sues MS Over Y2K Bug
>>>>>
>>>>>Yeah, it's really the developer's fault if she didn't "SET CENTURY ON"... Maybe someone should also point her to Y2KFOX as a solution for the FPD 2.6. I wonder what the lawyer will charge the programmer once he finds out how bogus a suit he has...
>>>>
>>>>What makes you assume the lawyer didn't know it was bogus when he took it? .........."Ah, we'll take a shot at it and maybe M$ might throw some money at us to make us go away...."
>>>
>>>The article clearly indicates that the complaint is with the lack of ROLLOVER, not SET CENTURY. Indeed there was no ROLLOVER in vfp3.
>>>
>>>It's still a nuisance lawsuit, though.
>>
>>Buf VFP 3.0 was not declared Y2K compliant. Only VFP 5.0 was.
>>
>>Dan
>
>It would have been nice if the reporter had bothered to check the facts about vfp, rather than expecting the (obvious) facts to emerge during discovery or trial. Science and technology reporting in the mainstream press is usually abysmal. I guess that reporters never want to pre-judge a case, no matter how dumb.
>
>It's a pity for us that she wasn't an ACCESS 97 programmer. As far as I know, its rollover function is useless because, in order to display a 4 digit year, you have to create your own 'yyyy' input mask, which then requires you to enter all four digits. Any workarounds would involve manual coding in the .LostFocus event, or something.

I think Access 97 has something like rollover, but it is a fixed date. I just checked, it is 29 (1930-2029). This means nobody can have a birthdate before 1930. It is not great, in my opinion. I plan to have a field in the configuration file to allow the user to change the rollover. Of course I will pop-up a warning if the ROLLOVER is a number that doesn't make a lot of sense (such as 29...). For us, 5 years ahead is plenty (in other words, we will never need to enter a date > five years from now) so a rollover 5 years ahead of the current year will be recommended and any change will result in a warning displaying upon each program load.

Joe

As far a manual coding, I am considering this to pop the field out to a 4-digit year entry with some kind of key press (Alt-4 ?). Thanks to inheritance, this will be a simple change if I choose to implement that functionality.

Take care,
Joe