Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Politics : Ask Michael Burke -- Ignore unavailable to you. Want to Upgrade?

To: BGR who wrote (61890)	6/9/1999 3:57:00 PM
From: Freedom Fighter	Read Replies (2) \| Respond to of 132070

BGR, In the U.S., much if not most of the updating and replacement of non-compliant programs, packages, and hardware is already done. So there should be no increase in orders related to Y2K of any kind as we move closer to the end of the year. If anything, there will be a big drop in IT business for the remainder of the year because all changes from this point on require very thorough testing in order to pass the much stricter than usual QA procedures that are in place until year end at least. Mostly, only emergency or critical business changes will occur for the rest of the year. Wayne

To: BGR who wrote (61890)	6/10/1999 7:38:00 AM
From: gnuman	Read Replies (2) \| Respond to of 132070

BGR, re: <A fine Y2K evaluation:> Did you forget the <g>? From the referenced post, y2k - investors who do their homework will find that y2k effect began jan. 1, 1999 and certainly june, 1999 as accounting and budgeting software (and other forecasting software) is already doing year 2000 analysis and number crunching so y2k is not waiting for dec. 31, 1999, it's already here among us and the lights are still on, computers still running that said, the psychology of y2k may have an effect in late fall on novice investors who haven't done their homework on y2k, or if a glitch by a large firm gets blamed on y2k (it's a convenient scapegoat for management bungling) Doesn't the Y2K problem have to do with recognizing the current date? Even non-compliant systems get that right in 1999. As for accounting and budgeting software (and other forecasting software), what about three and five year plans. Using his logic, the problem should have been encountered years ago. <g>