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.

Technology Stocks : Oracle Corporation (ORCL) -- Ignore unavailable to you. Want to Upgrade?

To: John Mansfield who wrote (3754)	12/5/1997 6:40:00 PM
From: Lizzie Tudor	Read Replies (1) \| Respond to of 19080

I know of one company that decided to convert to Oracle order management rather than deal with y2k issues in their existing legacy systems. Of course this would have been a fair strategy had they decided to do it in say, 1996. But since the deal with Oracle hasnt been announced yet (meaning, they havent started, no staff, etc.), this will give them less than 2 years to pull off the conversion and if they cant....kaboom!! Hopefully there arent too many shops like this, but there are a few. Michelle

To: John Mansfield who wrote (3754)	12/20/1997 4:54:00 AM
From: John Mansfield	Read Replies (1) \| Respond to of 19080

Y2K-ORACLE - Y2K remediation in Oracle applications dbmsmag.com Found on www.year2000.com This article contains lots of interesting tips for remediating Oracle apps. John ------------------- 'Thousands of Oracle-based applications in production at the turn of the century will have been developed before the industry became Y2K-aware. The purpose of this article is to review two key Y2K issues for Oracle-based applications: the default date format and dates stored in number or character columns. My goal is to provide a "heads-up" to the folks who are responsible for maintaining such applications. Although this article focuses on Oracle, you shouldn't take this to mean that you are off the hook if your applications run on another DBMS! Any application that stores dates in number or character columns may have Y2K issues regardless of the DBMS it uses. ' ... This is a built-in windowing solution in Oracle 8: 'DD-MON-RR to the Rescue ... Given that there is such little downside risk from making this change, it's surprising to find that the initial release of Oracle8 is still shipping with a default date format of DD-MON-YY. Regardless, the bottom line is that you should give serious consideration to changing your default date format to DD-MON-RR. '