"... best suited for experienced information professionals." --
BYTE, 08/97"... clearly and concisely explains the problem then provides a 5-step strategy (awareness, assessment, renovation, validation, implementation) to solving the crisis." --
Computer Book Review, 9/97"./#./#.a clear plan for facing and resolving the situation in this remedy-oriented coverage." --
Bookwatch, 5/97"./#./#.a well written book" --
Com.Links Library, 4/97"The Year 2000 Problem Solver explains not only how to deal with the technical aspects of your year-2000 problem but also how to handle it from a management perspective. Ragland believes that because the problem is pervasive across almost all systems, management must be concerned with interfaces, the timing of the implementation, and how to ensure that users are kept happy. There is also a helpful chapter on the costs of solving a year-2000 problem. The book includes a glossary of terms, a resource guide, and a thorough index." --
Infoworld, 07/97"This book explains the problem in clear concise terms and provides a strategy in the form of five step process for individuals and companies to combat this looming crisis." --
Charlotte Sun Herals, 7/97"This book is a practical gateway to the future for corporate managers, information managers, academician, and home personal computer users. It is easy to read and will be useful as a collateral text on "Year 2000" research issues" --
Washington Science Books & Films, 7/97"This concise guidebook, by Bryce Ragland, is best suited for experienced information professionals. To get the most out of this book, you should understand the Y2K problem and the programming consequences. Of the book's 270 pages, 165 are devoted to a bibliography of article references, analysis and coversion tools, vendors offering conversion services, help resources, and case studies. Instead of focusing solely on fixing applications, Ragland correctly places higher value on the data itself. He discusses how to keep existing legacy data from being corrupted during conversion of existing applications or by updates from newer Y2K-aware applications. Ragland's recommendations, such as creating task teams and motivating upper management, are appropriate to larger, enterprise settings." --
BYTE Magazine, 8/97"This, too, is a well-organized overview, but it's much less detailed than the Ulrich and Hayes book. The author dispatches year 2000 testing, which can comprise half of a year 2000 effort, in a mere six pages. The last half of the book is an exhaustive list of year 2000 tools grouped by function and platform. Normally, that would feel like padding, but if it helps you find a tool for those old WANG VS applications, it could by itself be worth the price of the book." --
Computerworld, 3/10/97
