Re: Question: How will the Year 2000 bug impact your work?

In article <54mbdn$1hs@decaxp.harvard.edu> torrez@law.harvard.edu writes: >Colin Thompson <Colin_Thompson@perth.ccmail.compuserve.com> wrote: > >>Ray Porter wrote: >>> >>>My point is >>> that the work required to fix it isn't technically difficult, just >>> boring and time consuming. We have over 3 years to get it straightened >>> out. There is absolutely no need for all the panic that some managers >>> seem to be experiencing. > >>That is an interesting point, but is it correct? Has anyone ever used >>software that calculates a future value for something? Like financial >>software?? What happens if you try to calculate a value past the year >>2000?? Yes, I saw problems last year with some systems calculating 5 year plans. Yes, the solutions are trivial for the most part. Yes, you need to actually run things to find some of these problems. No, it is not a big deal. Yes, it will be a big deal for some idiots who haven't thought to look for problems. Yes, the media will blow this all out of proportion. > >I have to think this would be the case with a lot of systems. I have >to get rid of all the "short dates" in our Access order entry system >before the end of this quarter because three-year payment terms are >standard for one of our products. Access hasn't been around that long, not much excuse for that problem. jg > >Terri > -- Joel Garry joelga@rossinc.com Compuserve 70661,1534 These are my opinions, not necessarily those of Ross Systems, Inc. <> <> %DCL-W-SOFTONEDGEDONTPUSH, Software On Edge - Don't Push. \\ V / panic: ifree: freeing free inodes... O