In the 1960s, the dawn of computing, programmers decided that it would be a good idea to use dates in their programmes. However, when they went through the code they needed, they found that once they put in the year 2000, the amount of code needed took a giant jump. Cleverly, they decided to just leave it out, deciding that modern programmers would easily be able to solve the problem. Most programmes still contain this flaw and purchasing the right corrective software may prove to be a minefield to the everyday PC user. This book aims to offer professional but straightforward advice on identifying system problems on all platforms, from PCs to mainframes, and describes resources for testing and fixing affected programmes. More importantly for large companies and corporations, the book tells the reader when its time to give up in-house efforts at fixing the problem and call in third-party specialists. Included with the book is a CD-ROM which contains sample code for fixing programs affected by the year 2000 problem.