Word 2003 Bible [With CDROM]

by Peter Kent, Brent Heslop, David Angell, et al.

Includes the latest information on security problems in Word and how to prevent them. Offers tips for formatting for black and white versus color printers Explains when to use Word for publishing to... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 076453971X
• ISBN13: 9780764539718
• Release Date: October 2003
• Publisher: John Wiley & Sons
• Length: 869 Pages
• Weight: 2.05 lbs.
• Dimensions: 1.9" x 7.1" x 9.5"

Customer Reviews

A wonderful book

This book helped me out so much when I was using Word 2003. The biggest thing it helped me with was marking indexes in Word. I would highly recommend this book to anyone using Word. You will probably need an updated version of this book if you are using a newer version of Word.

Another Great 'Bible'

These books are thorough, as is this. It is a compendium that I always keep at my desk.

Great Word Book

This is one book that the Word user should have in their library. I especially like the fact that it is the only book I have found that addresses the subject of field codes in some depth. It is a good source and the explanations are detailed enough for any user to follow. You won't be disappointed buying this book for sure!

Word 2003; A Great User's Manual for a so-so product

I have to admit my bias up front; Wiley Publishing produces quality books, and I always give them the benefit of any doubt. Likewise, their "Bible" books on Microsoft software are as good as one can find anywhere, and I would include Brent Heslop's, David Angell's, and Peter Kent's effort on MS Word as being as close to the definitive standard as one can hope for. Unfortunately, MS Word has more glitches than authors have time to write about, so troubleshooting Word takes much longer than a quick reference to this book might seemingly require. In fact I bought the book with the idea of establishing a dialogue with the authors about Word's disfunctionalities that they do not address, and perhaps may be unaware of. On the other hand, reading the book and practicing what it teaches is the best way to become proficient, and to be able to converse intelligently with others about the nagging, intractable issues that prompted some of us to buy the book in the first place. At something over 900 pages, users should expect to spend a great deal of time absorbing the knowledge that the authors impart. Even though I have been a Word user for more than ten years, I'm confident that this book will be a constant reference on my desk, either until I retire, or, more likely, a new version of Word comes out, and, Sisyphus-like, then we start all over again. What I would like to see is a book along the same lines that addresses trouble-shooting Word, in its various manifestations. With its multitude of ways of accomplishing specific tasks, Word, to me at least, resembles a house with many doors and passages linking its various rooms, but with a leaky roof, and various other structural anomolies that make using it frequently difficult. For example, on page 746, the authors discuss trouble-shooting peripheral devices, such as scanners. Not much is said about the primitive scanning program that Word includes in its suite of tools that may, or may not, interface will with scanning software. Now, one could say that's a mere quibble, as practiced users can generate Word documents very nicely. Well, true, but some of us do need to include non-Word pages in our documents, and store them along with our self-created ones in the same file. What to do. In the past I was able to import those materials as graphics onto blank Word pages; but keeping them in place can be problematic and often tenuous at best. I think authors of practice manuals like this one should be our advocates as well, someone who can grab Microsoft product managers by the collar and say to them, "Fix this! And while you're about it, do this or that also." Another glitch, and one that I live with every day, is Word's tendency toward corruption in its Normal file, so that customized toolbars do not last beyond a particular session. Why this happens, I have no idea; but others experience the same problem, and they have no answers, either. I pray that the Authors will see their way clear to addres