> I realised that I could be accused of the same error that
>gave us the millenium bug, BUT... the Cobol programs that
>are being converted are not 90 years old, more likely 20 to
>25 years old at most...
>
> Also it is a lot easier to change one function than to
>expand the size of a field in a fixed format file!
>
> Perhaps my function should look like this:
>
> function LeapYear(tnYear)
> ** July 11, 1998
> ** This function will self-destruct
> ** in 101 years, 5 months, and 20 days ...
> return (tnYear % 4) = 0
>
>
>Peter :-)

Sorry, my comment was not directed towards you or your code. It's just NOBODY really knows how long a particular piece of code may remain in use. Its just so strange that code that I wrote back in the late '70's early '80's (there's that Y2K problem again!) is still in use today, even though it only had a 5 year or so projected life span (THAT code will work until 2012). We used to do alot of work for a large corporation in Canada on a 5 year phase-out of their original system. They're on about their 5th "renewal" of that 5 year plan! And there is still no actual replacement in site (at least their Y2K thingie was addressed YEARS ago). Oh, well, you just never know! Remeber what happens when you "ASS-U-ME" things!

At least you've now "documented" the impending doom! :)