For example, a bank transaction on the 25th of July 1997 would be recorded as 07/25/97. Many software add the value 1900 to the two digits code to calculate the actual year.

A credit card charged on 1st of January 2000 would have to bear the interest of 99 years because the transaction date would read 01/01/00. This means the computers assume that the same transaction took place on 01/01/1900.

Another major problem with six digits dating occurs when we tend to compare the pre and post - 2000 dates. For example, 01/09/99 and 01/01/00, when converted into a simpl

A rough estimation to create solutions for the Y2K issue concentrated on something like US $400 -600 billion dollars worldwide. An additional 200,000 COBOL programmers will also be required.

Organizations are not the only ones that are going to suffer from the virulent millennium bug, it can be anyone, even a personal computer user.

Various reports stated that by the turn of the millennium, as much as 50% of all businesses which failed to address the year 2000 challenge would fall apart. Besides being deadly, expensive and extensive, the year 2000 problem affects hardware (BIOS, real-time clocks), embedded firmware, languages and compilers, operating systems, random number generators, database management systems, transaction-processing systems, banking systems, PBX, flight scheduling and any other system that deals with dates.

Only a few systems could be spared from the Y2

Some common words found in the essay are:
, leap divisible, 1st january 2000, leap divisible 400, 1st january, january 2000, considered leap, divisible 400, leap divisible 4, divisible 4, 990901 000101, considered leap divisible,
Approximate Word count = 594
Approximate Pages = 2 (250 words per page double spaced)