The majority of this paper will develop a plan on how each of the businesses and Government agencies should attack the Y2K problems. There should be a logical approach to planning how to investigate, test, validate, and if required, develop a contingency plan for Y2K. The job is to either form a team of personnel or hire a consulting firm to assess your situation. The team should employ the following steps: assess the system, renovate the system if necessary, validate the renovation if necessary, implement the renovation if necessary, test the renovation if necessary, and finally have a contingency plan in the event that renovating the system is not feasible and/or is too late. The only necessary or required action is to assess the system. This will be discussed in detail in my paper.

What impacts are they're to Government, Industry, and Small Business?

What can Government, Industry, and Small Business Do to Combat the Y2K Issues?

Another issue is all the databases that are used. Relational databases use date fields as part of wildcard actions, used as sorting identification, as grouping actions, and as part of daily identification. Some specific examples are: simple databases, such as the window explorer allow you to view and sort files in a date/time field. If this date field were only two digits, then it would incorrectly sort the files (year 00 would be first rather than last). Another example is a large database that is used to match names with addresses and billing statements. This database would need to flag dates with the billing statements. If the dates were incorrect or not sorted correctly, then the billing statements would be invalidated.

4. 28 February 2000. At midnight, the date should roll over to 29 February 2000. This is determined in the software by an algorithm that checks to see if the current year is a leap year. If it is a leap year then it should roll to 29 February 2000, if it can not determine the leap year, then it will jump to 1 March 2000.

The different application software packages that are available for computers are beginning to fix the year 2000 problem in the next revision and/or update. The problems that are being encountered are that the updates may not be compatible with the data that goes with the application software. An example is that Microsoft Access 2.0 is not year 2000 compliant. To upgrade to a compliant version, the original data associated with Access 2.0 will not run on the upgrade version. In addition, the upgrade Access will not operate on the old versions of Microsoft Windows. Therefore, additional problems are beginning to come into focus with the year 2000 issue.

Some common words found in the essay are:
Government Industry, FY99 FY00, Microsoft Windows, Y2K Y2K, Government Businesses, Department Justice, Y2K Issues, Nations Bank, Federal Local, Business Dates, y2k issue, government industry, y2k issues, application software, government industry business, february 2000, industry business, software companies, y2k compliant, combat y2k, industry government, 29 february 2000, dates fiscal dates, julian dates fiscal, fiscal dates calendar,
Approximate Word count = 2804
Approximate Pages = 11 (250 words per page double spaced)