MS

Writing soap notes is exactly what I needed. It not only shows you how to write soap notes but also has exercises for you to complete. The correct answers are included in the back of the book. I would recommend this to any health care professional needing to learn or improve their soap note writing ability.

As an early-onset Parkinson's person, I read as much as I can about good nutrition. I believe Ms. Holden's title that to eat well means to live well with Parkinson's. So I was pleased to have the opportunity to learn more when I discovered Holden's book, Eat Well, Stay Well with Parkinson's Disease. I bought it. However, I was disappointed with a salad bowl of worn-out nutrition theories.

She dishes out page after page of junk food advice. Let me give just one example. Why would a nutritionist recommend recipes (p. 111) that include a quarter cup of vegetable oil, which food professionals know oxidizes into compounds that damage the cardiovascular system and promote cancer? Most vegetable oils people buy are extracted from hard seeds with heat, pressure and chemical solvents. They're dangerous, especially to Parkinson's patients.

But it gets worse. She's even got recipes that call for margarine! (pages 112 - 113) in spite of well-recognized research on the danger of trans-fatty acids.

And of the 161 pages in this book, about one-third are general references on Parkinson's: appendices which include pages of product outlets, with such helpful products as "Lighthouse" for the blind (p.141), and lists of national Parkinson's groups which anyone associated with the disease has already.

Plus there are lots of pages of blank paper for "notes". And just in case anyone has a good idea on nutrition they can send it to her on the one of the four order forms provided for more copies of her book. The final insult is the inclusion of just awful poetry, like a 28-word stinker that takes up a whole page (74).

Don't buy the book.

This book has proven a godsend for my mom (who suffers from Parkinsons) and myself. The information is sound, easy to follow, and presented with ample background. I like the writer's approach to nutrition (i.e., good flavor is essential). Her knowledge of Parkinsons is impressive. I can't begin to tell you how many questions it answers. I consider this book an essential part of my mom's medical "team."

One of the most enlightening books I've read regarding Parkinson's Disease. Focusing on nutrition and what your body is going through with PD, it is a primer for what to watch out for, how to deal with dietary challenges, and what to expect. This book will help you make a nutritional game plan, and prepare a pre-emptive strike against most of the common surprises PD throws at you. I don't suffer from PD - I'm a family member. It was great for me and great for my family PD-er. I recommend this book to everyone interested in living better with Parkinson's.

This book generally covers many topics well, but DO NOT use this as a reference for those tricky issues or poorly documented features. Often when programming with Access, you need to lookup specific features or functions that either are not covered in the online help or not generally known. Without fail, I never seem to find these sorts of topics covered in this book. If you are a beginner and want a general overview, then this book is fine. If you are a seasoned developer and need a reference book for Access programming, I would definately consider purchasing another book.

I am a clipperhead having to learn how to use access. My concern is to learn how to use access to do data conversion, manipulation, processing w/o much of the visual user interface. This applies to processing edi flat files, structuring collected data, ect.

This isn't a visual book. Just good old procedural programming, stuff that clipper was great for.

The book does a good job of showing how to manipulate a database at the non-visual level. As I spend more time with it, I will do a follow up. For a programmer trying to figure out how to do the backend, non user interface programming of an application, it gives you a start.

Wes, Clipperhead since Summer 87

I mentor new VBA programmers and I have 4-6 VBA books in my library that I use for the code snippets. This book is the most useful by far for that task. The book has more code examples than any other book I have and the explainations are relatively complete. I have found a couple pieces of code that are incorrect or very poorly coded--but they are few and far between. The book covers a couple of things very well. DAO and ADO are covered in depth (these two chapters consume about 25% of the book) as well as providing good explainations of form and report events. This is a must have for the beginning programmer.

This book has little or no real content. It looks good on the surface but there is nothing underneath.

In the interest of system safety the author has left out so much information it leaves the book essentially useless. Worse, it gives the impression that some of the things you may need to do can't be done.

This book may be okay for teaching children a limited use of dos but anyone that has any judgement at all needs more information.

like I said, good book, but a bit outdated. The author talks about 50 MByte disk drives as being huge and about 5 inch floppy disks. This is like reading Aristotle's physics instead of Newton's. If you use DOS it will help you of course, but ignore most of the talk about hardware. Covers DOS commands very well. Contains interesting trivia about computers too (the life span of a hard drive is about 4 years, unless this is outdated too). To conclude, if you use DOS, it will suite you. Even better seem to be the DOS reference book for Dummies.

-----DOS for dummies is the most helpful computer guide I have ever laid my brown eyes apon. It has everything from turning on the computer to editing you configuration files. It has several jokes about PC's and even some cartoons! Whether you just got your computer yesterday or you MAKE computers this book is helpful. In the front it has some cheat sheets and quick refrence guides that are really helpful. I have had this book for 2 years now and still find myself reading it. -----So even if you don't plan on spending time in DOS (which you always end up doing anyways) GET THIS BOOK!!!!

GC/MS should be helpful to the novice or student who has never used GC-MS before and who has had minimal experience with GC. It is a little disappointing that about 20% of the text covers material about GC that any experienced GC user should already know.
The book contains an easy to understand explanation about how a mass spectrometer works. Some additional details or diagrams could have clarified the description of how the DC/RF field separates the mass fragments in the quadrupole analyzer; but otherwise the text is crystal clear. Information about tuning and maintaining the mass spectrometer is well presented and the authors provide some helpful suggestions including a way to tell during the tuning process that the source needs cleaning. More information about spectral interpretation would have been appreciated but is probably outside the scope of the book.
This book belongs on the library shelves of colleges with undergraduate chemistry programs and would be helpful in industrial and environmental laboratories as an introduction for chemists and technicians new to the field.

The book may be considered difficult for a starting user. I have been working with GC/MS for 10 years and the coments and all explanations inside are really and absolutely useful. Unfortunately I had not such a book when I was starting to deal with this technique.

It is a good atlas for a trainee. It includes difficult part of body with a precise label. However, it is not easy to find the one that you want since there are plenty of labels. In addition, I think it is much better if there are few sentences to elicit the information concerning the radiological imaging like certain common normal variants that one could see in the radiological imaging

I highly reccomend this for MRI and CT images viewing. The images are very clear and capture the area of interest very well. Medical professionals will sure can rely on this atlas for normal images.

I reread this book to see, why I didn't like it much, it didn't take me long to find out. The author seems to think it's wrong if women want to practice celibacy or try to remain a virgin until marriage. She doesn't think that's something to be proud of. Now my problem with that is if young girls that are planning on trying to wait until marriage read this book might think that's something to be ashamed of, or they want be able to please their spouse if they have not been practicing. I think more open minded people, probably enjoyed the book more so than myself.

Max Elliott's book is a must. For those of us who have not found our true self, this book will help uncover what is buried or lying dormant. It shades light on darkness. Some of the references may seem a little too much or farfetched for some, but there is certainly a little something for every female. The book is to share. Don't just read the book, but make your friends and co-workers aware of it also. It is an enlightment.

You've probably read everyone's glowing reviews, so I'll get to the point. Although I found the book EXTREMELY useful (I use it so much, the pages are coming apart), but it has two serious flaws:

#1: The book lacks any serious examples. It leaves the novice reader (and sometimes the near-expert) guessing. Why not a CD full of examples?

#2: There is NO INDEX! Who writes a book nowadays and doesn't include some form to find information other than the TOC?

Outside of these two problems, this is a higly effective book and its not just for InterDev users. The information provided will help anyone using JScript, VBScript, DHTML, and CSS.

If you go to the online help for Visual Studio and select the VID view, you get the same info that's in this book. That's not all bad. I like the linear presentation and organization real-view of the book. I purchased Amundsen's _Using VID 6_ as a first book and missed the useful catalogue type listing of ALL objects, methods and properties. In the help files you have the hotlinks, that's about the only difference. Be forewarned, even with a User's Manual & Programmer's Ref, VID does not give sufficient examples for the novice or even an intermediate programmer. Pretty big intuitive leaps are needed to arrive at what seems a simple logical step. The VID Web Ref helps by providing a linear view of multi-dimensional hypervolume.

This book is a one stop resource for HTML, DHTML, JScript, VBScript, and ADO. Everything is in here including the kitchen sink. But definitely not for the novice, this book assumes a certain level of proficiency from the reader.

It's a shame to see so many negative reviews of this book. I am an instructor and was very happy to find this book. I have never found another like it that covers the territory to train people in DOS, how the hardware is set up & works with the Operating Systems, and especially how we use DOS to make changes to the Windows environment (other than through the Control Panel).
I teach a PC Specialist Course that has a goal of training individuals to work in this field by training others and trouble-shooting system problems. We touch everything from how the system is put together, installing hardware & software, using MSOffice to advanced levels, VB Programming, DB management, Networking installation & setup basics - all of this in 9 months. We don't have time to read through a "Dummies" book to pick up just DOS, and then Windows, and then system hardware, and then....This book encompasses all of these things. We've got 3 weeks to understand the workings of DOS, Windows, and the hardware at the introduction of the class. Many concepts have to be covered. This book is the only one I have found that does it - and in "laymen's" terms.
Being an instructor, I wondered if I am biased. So I asked my students - who range from mucho PC experience to those who don't even own a computer. Everyone found the book more than helpful, a great teaching tool, and good reference to go back to.
I would like to see two pages on the Fdisk command - no more is needed for a PC trainer/support person. Fdisk is a last resort in most cases and not a common occurrence. And the need to know is not much more than to type the command, partition it, and go - add the MBR switch for dire circumstances. Some of these concepts are discussed in the book.
This is NOT a DOS book. Read the title again. It is what it says it is.
Carolyn & Bette - thank you.

There is an old saying, You get what you pay for. I feel as a IT student, that I have received my money's worth, many time over. I've played around with computers for a few years and now that I've decided to make a career change an learn how to repair computers I felt I needed to take some classes in area where I needed help. This book will help you no matter what level your computer skills are at. It starts out at the entry level for beginners and advances on to the practical level and then goes onto the advanced levels. Probable my favorite feature of the book is that the authors have created test files and directory for you to work with, so you don't have to worry about messing up your own computer. I'm almost done with the book/class now and I've already used many of the commands and batch files. I had formatted a hard drive before, however I had never low level formated a hard drive, this book took me thru that as well. If your someone who just wants to understand a little about DOS this is a great book. If however your an IT student who plans to go to a universities, this is a MUST HAVE book. Universities expect you to already have this knowledge and usually don't offer such classes. This book doesn't just give you a list of commands with diffentions, it gives you a complete explanation aswell as sample files directories for you to practice on. Remember as they say practice make perfect. Great book for anyone at any level who want to learn more about there computer.

This books focus is to teach the reader how to properly use the windows command line NOT DOS. It explains why the command line is important, even for todays users. It is more effecient than say...windows explorer. This book explains in detail many of the wonderful commands available to you including FDISK and others. It also explains very well how to incorporate many commands into batch files that can easily automate seemingly comlpicated tasks. This book is great as a reference and a learning tool. To those who complain that they already know DOS, this book does not intend to teach you DOS rather it teaches the windows command line and how it can be used today. Command lines are frequently used by many windows users and by networking proffessionals as well to create logon scripts (which is another topic that the authors bring up). Overall I highly recommend this book to all students who use windows or plan to enter a networking proffession.

I can't believe how bad this book was. It gives simple concepts and then beats them to death with pages and pages of code. The author only touches on the truly difficult problems and refers the reader to web sites for the real material. He fills the pages with endless prose containing little substance.

I bought this used for $5 and I paid too much.

Unlike beginners who gives a book 1 star because they cannot compile the code, this should be even worse because there is no code to compile! Yet there a ppl giving 4 or 5 stars!.

It is unbelieveable that people can find the code or ideas in the book useful. Anyone who has played an RTS games KNOWS what and how a RTS is, yet the author seems to explain what is RTS (with screenshots) in the first few(many) chapters of the book.(Wasting pages)

After reading this book ten times, I don't find myself any closer to making a RTS and that is mainly due to the fact he doesn not teach you how to do program, but rather what should be done. You have to read thorough his code (badly commented and explained) to really understand but if I wanted to read code, there are plently of free engines on the web. Not to mention the code is very buggy ( I found 3 bugs that I have confirmed with the author).

Most of the ideas can be found on game development sites, nothing too new there. For people who says they can understand the code, I can only think they are using his engine or already know how to do RTS. REAL PROGRAMMERS WANT TO WRITE THEIR OWN CODE. They want to understand how to do something, not call someone's engine(or debug ppl's code.)

The plus side is that it is the only book that attempts to cater to intermediate programmers, though I don't see why intermediate programmers needs anymore line drawing and clipping code. There are some (few) points that you wouldn't find in a beginner book (like other books) but not really worth the price. Plus side, author is indeed friendly as many claim though I wonder what games he actually does with his buggy engine.

And what is with the 5MB CD? where has the 650 MBs gone? At least show me what the engine can do, if it is really builds up to a RTS game.

The book is fairly out of date at the time I'm writing this, but I had hoped when I picked it up that it would have some valuable tips for writing games that are relatively timeless. The DirectX API has certainly changed a great deal from 6.0 to 9.0, but good game architecture doesn't change much.

The book was disappointing. At times it reads like a collection of disjointed articles written by an amateur programmer, and at other times it demonstrates a clear "been there, done that" presence.

Many aspects of the book are, simply, annoying. After briefly mentioning the Age of Empires scenario editor, the author writes in a separate note offset from the main text: "I worked on the scenario editor and it is largely the same as I programmed it to be, at least functionally." This self-important commentary does nothing to promote anyone's understanding of game development.

The author's programming skills are poor. Other reviewers have said this; no need to beat it into the ground. I get the sense the author was working on tools for the games he worked on, not the games themselves. This comes out in the text: good explanations of the game development process and tools used by animators and developers, but shaky descriptions of game architecture.

The choice of topics is a mix of good and bad. The early chapters on planning are very good, but then we get into a very long chapter on painfully optimizing line drawing, complete with a bad clipping algorithm ("Actually I wrote it myself without any help.") The chapter ends with, "but also realize that there isn't much line drawing in games these days", calling into question the purpose of spending so much time on it.

It does have a long chapter on pathfinding, which was nice to see.