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

In article <5581l5$b8c@shadow.CSUFresno.EDU>, stevec@zimmer.csufresno.edu says... > >Why not write a function that will NEVER need to be changed. It is >surprisingly simple, and here's how... > [algorithm snipped] > >Using this method in 1997 returns 19 for the century for years 08 >through 99, and 20 for the century for years 00 through 07. Each >year, the algorithm advances one year. > >This "sliding century algorithm" will ALWAYS work because it starts >with the current year as its base of calculations. First, this is not what I want at all. In some cases I'm dealing with birthdates and I want the century to fall backwards instead of fowards. (98 = 1898) In other cases when I'm calculating AT&T pensions, I want a fixed cutover year of 1978, divestiture. Second, why should I be coding at all. I want to set a parameter and have this switch over happen without programming. I'm currently using Progress, which does exactly that. Some sessions get started with one parameter when they work on one part of the application, other sessions get a different parameter for a different part of the application. ====================================================================== Geoff Crawford Phone: (201) 627 - 0307 Innovative Client Servers FAX: (201) 627 - 0634 24 Dogwood Drive Email: geoff@innov8cs.com Denville NJ 07834 Web: http://www.innov8cs.com