>>>>>>Learned of this today. Anyone know anything?
>>>>>>
>>>>>>MICROSOFT SUED OVER Y2K BUG IN DATABASE TOOLS
>>>>>>Software developer Ruth H. Kaczmarek has filed a lawsuit in U.S.
>>>>>>District Court against Microsoft, alleging that the company's
>>>>>>FoxPro and Visual FoxPro database development tools were unable to
>>>>>>process dates properly beyond Dec. 31, 1999. The suit is believed
>>>>>>to be one of the first against Microsoft alleging Y2K defects in
>>>>>>its software. (Bloomberg News/Seattle Post-Intelligencer 11 Dec 98)
>>>>>
>>>>>Hi William,
>>>>>
>>>>>I've done a couple of web searches and can't find anything on this. About the only thing she can claim wasn't Y2K compliant was LUPDATED(), and that was fixed in 6.0.
>>>>
>>>>The article was published in the Seattle Times. The woman was upset because when she typed in two digits it could not read her mind and tell that she wanted the year 2000 not 1999. I have no idea if she is using the rollover feature or if she even knows what that is. "Kaczmarek claims that when two digits are entered for a year in the 21st century, the entry is stored and processed as a 20th century date." Apparently its a class-action suit. The site is www.seattletimes.com/news/technology/html98/bug_121198.html.
>>>>

Of course if she was a member of UT then she'd have known better. :-)))))))))))

I don't know about any of you, but I've been writing dates on cheques etc. as MM/DD/YYYY for the past year and a half at least. I've converted my self to writing a 4-digit year. If I was developing software that required date input in MMDDYY format I'd be forcing the users to do likewise. Right now, all the dates I'm using are julian for the day of the year only (don't ask!) At the moment I don't have anything that will roll over the EOY/EOC/EOM.


Jen