EG Books

This book could be easily misconstrued and misapplied by new-comers to psychotherapy, as the methods described would be appropriate to a very small minority of clients - highly repressed, anxious, guarded children - but the book prescribes the method for children in general. When reading it, one gets the impression that it was written during Freud's time, when repression and suppression were common barriers to treatment and common foci of treatment. In today's world, few children suffer from extreme inhibition and repression, and are thus in need of disinhibition and liberation from extreme guardedness. Instead, most children receiving mental health services (I work in an agency specializing in this) are struggling with understanding limits and are already overly-disinhibited. They are in need of nurture and structure combined. Moustakas' methods of no-limits play therapy might produce some therapeutic revelations, but are also likely to generalize to further disinhibition and increased impulsivity and disregard for structure, limits, norms, reponsibilities, and consequences. In less formal terms, this book gives the reader a good formula for making a spoiled brat. We don't need more of those. For the veteran clinician, who can read this book and take it with a grain of salt, a few methods are described that might be good in a few specific situations. If you're new to the field or to working with children, please run the other way if you see this book on a shelf or website.

It is apparent to me that one reviewer here who is criticizing the book, did not receive his or her education at the very graduate school founded by Clark Moustakas. When Dr. Moustakas comes into the classroom for his annual lecture in play therapy with his plaid suitcoat and delivers moving words and then, in a very Morrie Schwartz kind of way, dances, and makes the class dance, you realize you are in the presence of a great spirit.

Anyway, without receiving instruction on this theory outside of glancing at the book, I could understand this person's interpretation of this theory. But there really are emphases on limitations (the book even provides an examply), and you talk about disinhibition in children today, have you ever worked with foster children, they are not the disinhibited children you are describing? I also don't see the Freudian overlap, existential psychotherapy is different. It is about providing an atmosphere where the child can be authentic in ways that his typical environment does not allow him. When he feels comfortable to express this, feelings are identified and reflected back, and appropriate ways to express these feelings are then explored.

Overall, this book offers a very human approach, and yes, it may be more appropriate for the intermediate play therapist, but the approach works more than you have confidence for when you hit that playroom for the first time but what I have learned through practicing the approach, is that you have to trust the process. If you go with it, you will see results.

This text represents the final publication of the founder of Existential, and now called, Relationship Play Therapy. Moustakas's text is definitive in this theory of play therapy. The book is written in existential prose with specifics given to direct the therapist interested in this particular theory of therapy with children. To find this book valuable, the reader must believe in the child's capacity for self-determination and responsibility. In the present environment of behaviorial contracts and brief therapy interventions with little attention given to the developmental needs of childrem, Moustakas provides us with a refreshing return to seeing therapy as a committment to personal growth and development between therapist and client. The methodology and theory are meant to encourage personal responsibility and understanding that goes far beyond the immediate problem. The reader can be easily deluded by Moustakas's prose and writing style into believing that this is a simplistic theory. The application of the theory presented is beyond the lay person and requires training in psychotherapy to be effective. However, the reading and style of expression makes for easy understanding of a complex form of therapy.

This isn't a true Songwriters guide, it's focused more on famous SINGER Songwriters. It includes only a small handful of only the most famous Songwriters that became recording artists. I can't imagine paying 175 for this. If someone hasn't done an encyclopedia of songwriting, they need to, and probably at least one Volume for each genre. Very disappointing.

Nigel Harrison's SONGWRITER'S is the definitive work for anyone interested in the craft and history of songwriting. Who wrote the greatest songs of all time? The answers are all there, in one fantastic volume.

More than a reference book for songwrtiting geeks or trivia pursuants, SONGWRITERS gives you the history of the people, as well as an indepth list of their work.

The writing style of Mr. Harrison is beyong compare. He evades the encyclopedic writing that is so prevelant in this genre with his witty and insightful comments throughout.

Every music lover should have a copy on their shelf, just as you'd have Norton's HISTORY OF WESTERN MUSIC. It is the next natural step in the musical evolutionary process. Reading SONGWRITERS will only enhance your enjoyment of the songs you know and love by knowing something about the people who wrote them. And the work is not without its mysteries. You'd be surprised to learn who has written some of your favorite songs.

An indispensable musical reference tome. Mr. Harrison has
gathered discographies on many of the major songwriters of
our time, combining it with information on the recording
artists who made the songs famous. I have found no other
book which provides so much useful information in this
manner. The biographical sketches are concise, and each
entry also lists co-writers and collaborators. A must have!

Please not that this book covers Outlook 2000 only. If you have Outlook 2002/XP this title is not for you.

When we bought this manual for the office (which had just switched over from eudora to outlook as an e-mail system), I assumed it would be helpful and at least answer many of the questions that various co-workers were asking regarding the software. I hoped that it would help us use outlook to streamline our office tasks and mailing databases as well. Unfortunately, we were ..... Not only is the book elementary (nothing new was learned), but there is NO TUTORIAL. Sure, there is a CD-ROM attached with the book, but the only files on it are a word file of something already in the book, directions on how to get to BCR (whatever that is) from the Denver Airport, and a diagram of a librarian. Why? No idea. We are returning this book, as it's not worth the money.

Using Microsoft Outlook: A How-To-Do-It Manual and CD-ROM Tutorial by computer expert Michael Sauers is a self-explanatory, "student friendly" guide to quick and easy utilization of one of the most popular and widespread e-mail programs today. From scheduling with Outlook's built-in calendar to managing one's contacts to customizing Outlook 2000, Using Microsoft Outlook has everything a businessman or lay user needs to know. The strongly recommended CD-ROM tutorial offers step-by-step instructions for even the most uninitiated of e-mail novices.

Good clear photographs, easy to follow text, variety of techniques. Geared for mid-teens to adult

This is a great book that combines the fun arts of needle felting and wet felting. The instructions are excellent and the photographs really help you create your own fiber pals. This book has energized me to create my own whimisical creatures...

I just recieved a copy of this title a couple of days ago and I thought I drop some lines here. It's a great book for those who want to learn more about Outlook forms, COM-addins, Outlook 2000 VBA and also how to access outside data within Outlook forms. It also covers useful hints that can't be accomplished with Outlook directly using other technologies like CDO etc.

They do a terrible job of getting novice users started. In the first chapter they lecture about knowing objects inside and out, but really don't support any means of doing that short of reading the Appendices and memorizing them without any sense of context. Basically, you already need to have a VERY strong background in VBA / VBScripting for Windows applications. If you are not a HIGHLY proficient programmer/scripter who is merely looking to turn his/her focus onto how to apply those skills to this specific (and peculiar) environment, FIND ANOTHER BOOK.

Chances are, if you're in the market to buy this book, it's because it's required for a class. This text provides a wide range of rhythmic exercises that are meticulously arranged in order to ease students through progressively harder territory. Indeed, there can be no doubt that a great deal of work was put into the creation of this book as a very useful pedagogical tool. (Though it should be noted that it is fairly useless for reference.) That said, it is a very slender volume for such a dear price--a very great expense for your average college student. Ms. Hall and her publishers should be truly ashamed to be driving such a hard bargain.

This book was loaned to me by my music theory teacher after I finished Ed Sueta's "Rhythm Spectrum". Unfortunately, I was practicing my rhythms, and laid the book on the floor in the basement so I could take a nap, and it, along with several other books, got ruined when the washing machine overflowed. So I inherited a good, but damaged book (I'm buying a new one for my teacher to replace the ruined one). And in the meantime, I'm reviewing the rhythms.

The thing that makes this book challenging is that it progresses in many ways with each new rhythmic concept. The concepts are similar to Sueta's method, but they require you to change tempos, follow dynamic markings and phrasing, and use multiple limbs (up to both hands & both feet), as well as speaking rhythmic passages.

The book advances quickly, and after completing Sueta's book (which is no walk in the park), the new challenges this book provide me are enough to make it a stretch to complete one unit a week.

While I would not probably buy this particular book had it not been for the unfortunate accident, I am glad to have it (wrinkled & slightly mildewed as it is) in my growing music-resource collection. It's a technique book, not a reference book. And for that, it is useful.

While the price is obscene, this is the sad fact with any textbook, and that is an issue that should be remedied through congress and your local schools. However, I do not try to make it a practice of rating books on the price. Since I rarely ever buy a book at the regular price (thanks to Amazon and my local used bookstores). So, my rating is despite the large price tag.

I also have the newer (corrected) version of the book (check the copyright page in the beginning of the book, mine lists version: 5 6 7 8 9 QWT 1 0 9 8 7). Despite the numerous corrections, I still find some errors, even those that are unlisted in the errata list. When looking at the four KB articles on the Microsoft site, the errata list shows a gap between part 3 and 4. So I think there is something missing in the errata.

For example: an error I discovered today, on page 712, the second bullet reads:

"One or more PrincipalPermission properties. Use Authenticated to restrict access to authenticated users, Role to restrict access by group memberships, and User to restrict access to a specific user name."

This is incorrect, there is no 'User' PrincipalPermission property. Replace 'User' with 'Name'.It should read instead:

"One or more PrincipalPermission properties. Use Authenticated to restrict access to authenticated users, Role to restrict access by group memberships, and Name to restrict access to a specific user name."

This is in particular a strange error, because on the previous page the authors says:

"Memorize these three properties (Authenticated, Name, Role). Remember, PrincipalPermission doesn't expose any other properties--not a user's full name, phone number, password, or any other attribute."

For the rest of the book, I found the topics are not very well explained. Except for the chapter dealing with Code Access Security, which I found was very clear. In general, I did not like the fact that there are so few images in the book that could clarify the text. Sometimes the text alone is a litte bit boring to read. But then again, it's part of the job, no?

As there is no alternative for this book yet, I hope I will pass my exam by using this book and some internet resources... We'll see.

Good luck to all exam takers!

Please note that the second edition of the 70-536 Training Kit is available. Fully updated and revised, the second edition replaces this first edition, and is the one to buy to prepare for the 70-536 exam.

I have just started studying for my certification for the .NET Framework and this book is real helpful. It provides me with answers that I was not able to get through school. I have learned some new things that make developing a bit easier now that I have learned about some different approaches with this book.

The majority of reviews of this book are quite right in that it is a good preparation guide, but the plethora of errors can cause some confusion. Microsoft has posted the corrections for the book, but the best way to overcome the errors is to go through the practice tests and look up questions you feel you are right about. Additional reading is a must and missed questions are the best prompt to guide you to additional resources.

While definitely a thick book, the content is extremely detailed. Though keep in mind that there are many ways to reach any given end or effect - the various authors programming / example styles expose the reader to a few ways to expressing the same result, which is quite beneficial.

In terms of organization, this book is very good, especially considering that multiple authors were involved. The only chapter that merits additional scrutiny is the security chapter, which helps throughout the book, as security considerations are sprinkled throughout.

In summary, with a moderate amount of experience with .NET (2.0+), this book is an excellent primer for the test and provides the requisite understanding of the framework to prepare one for the exam. The only caveat I found was that for people with .NET 3.0 or 3.5+ experience, some of the methods may be a slight bit different due to minor changes between 2.0 and 3.5.

After having purchased book and used it to study for the 70-536 exam. I can summarized my experience in the following:

The book will not be sufficient to pass the exam, and makes for a really bad and frustrating study guide.

The authors of the book that have an incomplete understanding of the material.

The authors and editors of the book have horrible writing skills.



First of all the book is missing much of content from the actual exam, probably about 40 percent. Don't let the books objectives insert fool you, there are huge gaps in the book, and you will not pass by using the study guide as your only resource. While the study guide is missing a lot of content, it also goes too far into detail for some content that is actually included in the book. For example, for the exam you will only need a broad understanding of reflection, you will not need to be able to write an entire section of code on "creating code in runtime", you will also not need to memorize the exact steps of using the .Net configuration tools.

Often it seemed then when the authors didn't understand an item, instead of researching it themselves and then thoroughly explaining it, they just cut and pasted random information / code examples from MSDN with no after thought, or they simply skiped the difficult item all together. It's understandable that the authors would have such bad knowledge of coding, since as they personally state that they have only written "hundreds if not thousands of lines of code" (pg 68).

Some examples of their poor understanding include:

The StrongNameIdentityPermission in the book (pg 661), is generically described as "defines the identity permission for strong names" , pasted verbatim from MSDN. A more complete and meaningful explanation would have been "Restricts the assembles that can call this method, based on a specific public key from the calling assembly."

On page 603, instead of actually explaining how to use the PerformanceCounterClass, the author instead find it necessary to show us how to append PerformaceCounter properties to a StringBuilder class.

On page 819, the authors the describe how to perform "Exception Handling in Managed Code". They quickly list how you shouldn't do it, and that "you need to do something else". Of course instead of actually saying what it is, and even mentioning the solution, they list a 2 page cryptic code example.

As of the second edition, there are still many code and grammatical mistakes. The authors often try to get cutesy with inappropriate personal anecdotes that feel completely out of place, or use bad worded filler material like "These two classes have an intuitive synergy that becomes evident when you use them." (pg 482).

Reading the book I got a feeling that the authors got paid per page written, so they felt compelled to stretch things out as much as they can with extra tables for class parameters and methods and unnecessary code examples. Mind you, instead of actually adding all of this filler material, they could have just been more thorough with the exam material.

Bottom line is that there is no excuse for incorrect code samples, grammatical mistakes, very poor writing, and missing content. Especially since this is already the second edition.

Some other reviewers of this book have stated such ridiculous explanations as: "i'm glad there's errors and that you have to research to figure them out." or "Places where this book is "weak" is where YOU as a reader need to learn how to use MSDN and look it up yourself." , those are NOT valid excuses for such as horrible book.

For a good example of a study guide see: Kathy Sierra's study guide for SCJD, even though that exam is much harder, the book is concise and straight to the point. Teaching you only what you need to be taught.



As for the actual exam:

It was easier then expected, especially when compared to the Sun Certified Java Programmer course (mind you I did purchase extra exam practice questions, and study from them).

Whereas in the SCJP exam, there are many tricks questions, and you needed a thorough understanding / memorization of writing specific code, and knowing when code wouldn't compile, run, etc. For this exam, having a broad general understanding of all topics will be sufficient, the most obvious answers are typically the correct ones, and you really don't need to memorize/ be able to write entire sections of code .

For study preparation I recommend reading through the book, without trying to memorize code sections. Skipping the labs. Purchasing extra exam questions like Transcender, and working through them, and looking up any missing items on MSDN.

It took me about 100 hours to prepare for the exam, but this is having already a solid understanding of Object Oriented Programming, having passed some Sun Java Courses, and having used .Net at work. I probably could have studied for less time, if I was warned about this book.

Also make sure to place special emphasis on studying streams, including all related streams types, crypto , compression, text, etc, and their corresponding method signatures.

I'm giving this book 2 stars, instead of 1, solely on the fact that that this is really the only 70-536 study guide in print, and using it will save you time over trying to figure things out using Microsoft's atrocious MSDN, which is just as poorly written and confusing.

I have some experience with C++. I felt the sample applications in this book were easier to understand and follow than the more complicated librarian example application in the Palm OS Bible by Glenn Brown (though it is a good book also). Granted this book does have problems with the code, and is based on an older version of Palm, the problems were easily worked through with the Palm provided documentation from the Palm website. One drawback is that the book does focus on using the CodeWarrior product, but again with a little effort, the samples can be easily ported to using the free PRC-Tools/GCC software. Actually if the Palm OS Bible and this book were merged, it would make a really great reference.

The book is pretty much outdated by now. The included version of codewarrior only works with Palm OS 3.5 while 4.1 is out. It supports debugging only through the serial interface, many new palms use USB, which will mean you'll need to get a serial to usb or use the emulator. The starter application didn't work from first time. I'm even pretty much reluctant to continue reading. Requires putting the palm into console mode with special key combination that didn't work for me. I have Palm Zire, with Palm OS 4.1, which is a resonable development platform I suppose.

I have some experience with C++. I felt the sample applications in this book were easier to understand and follow than the more complicated librarian example application in the Palm OS Bible by Glenn Brown (though it is a good book also). Granted this book does have problems with the code, and is based on an older version of Palm, the problems were easily worked through with the Palm provided documentation from the Palm website. One drawback is that the book does focus on using the CodeWarrior product, but again with a little effort, the samples can be easily ported to using the free PRC-Tools/GCC software. Actually if the Palm OS Bible and this book were merged, it would make a really great reference.

Typos ! More Typos ! Still more Typos !

Basic errors of fact .

Out of date material !

It is all here.

Save your money.

Spend it on... a better book from Amazon.com !

The cover claims, "Open This Book as a Novice and Finish It as a Pro". I found it useful, in a very utilitarian sense, because I am a fairly experienced C programmer, but a true novice would be hard-pressed to get anywhere with it. A modest amount of experience with C/C++ is an absolute minimum prerequisite, in my opinion. As mentioned by other reviewers, the title, or at least the cover, should indicate that if you don't plan to use CodeWarrior, you shouldn't bother.

While I was able to work around them, there were a couple of things that I found very frustrating in this book.

Since it was written for Palm OS 3.1, quite a few of the data types used in the example code have been deprecated, and the code will therefore not compile without including PalmCompatibility.h in addition to the normal PalmOS.h. The author now has some information about this on his web site, but it was not available when I first bought the book several months ago. I figured it out, of course, but it was an exercise in frustration.

More troublesome to me is the disjointed, difficult to follow, rambling explanations and not-so-subtle errors in the text and example code. The example code frequently doesn't quite match the explanations. In at least one case (chapter 4), the author could not possibly have tested the code in the listing at the end of the chapter; instead of using a call to the PalmOS library function FldSetTextHandle, he mistakenly typed FrmSetTextHandle, which does not exist in the PalmOS library. In my opinion, failure to test the code destined for publication is unpardonable.

Having said all that, I still found the book useful, as I said at the outset. Perversely, the glaring mistakes actually helped in a way, by forcing me to go to the Palm documentation and header files to figure some things out for myself. Since I was completely new to PalmOS programming, I did learn a great deal in the process of going through this book, although I would have preferred to get there with less heartburn.

Great review of "the essentials" given before getting into the meat of the text, including ways to help determine key sigs, etc. Audio CD a big help.

My first complaint is that there is no reason why this book should cost as much as it does. It has flimsy paperback binding (I owned it two months before the cover fell off, and my only use of it was during class and carrying it on the 2-minute walk from the music building to my dorm - in my hands!) and cheap paper. The only "pictures" are some black-and-white staves. My psychology book cost as much as this book and was physically made far superior. The only thing I like about the pages is that they accept pencil, which is nice for taking notes and jotting down answers to questions that can be erased later.

The set-up of the book itself makes sense and was fairly easy to skim when preparing for a test. I appreciated that. Yet I think all the good I can say about this book has now been stated.

As other reviewers have indicated, it has lots of errors. My theory teacher had to correct several factual errors in class, which made me worry about the rest of the book! Also, most of the "review" questions in the book don't have answers - which make them completely useless. I saw no point in practising skills if I didn't even know whether or not I was doing it correctly.

Also, I used the book to study so I could test out of Theory I, and was aggravated to no avail that the book does not really explain figured bass - the foundation of all theory! It mentions figured bass, assumes the reader knows what it is, and proceeds to teach new concepts. I had find websites to show me figured bass, thanks to the lack of explanation in my theory book!

Chances are, you don't have a choice whether or not you use this book, since, like I, you are coerced into using it because of your professor. In that case, be forewarned about the problems with it. However, if you do have a choice, only use this book if you can find it for $20 - that's about how much it's worth. And get supplements; you'll need them.

this was the text book that was used in my college intro to harmony and tonal counterpoint. it was full of mistakes and was very difficult to follow. my professor even expressed his hatred of this horrible, horrible book, but yet my university feels inclined to continue using it. if you really want to learn voice leading and harmony, find another book.

This is a well-designed book, but is marred by an incredible number of mistakes. It's truly unbelievable. I realize that these exercises can be tricky, but the publishers ought to be ashamed that, after four editions, they have allowed mistakes to remain in nearly every assignment.

Why is it that the majority of first-semester music students can find so many mistakes, yet the professionals who put the material together can not see glaring errors that jump right off the page? This is the most unreliable text I have ever used. It's not unusual to find a mistake here and there in technical books, but I identified literally dozens in just the first half we covered in Theory 1 class.

If you are required to use this book for a class, then you don't have any choice--just be very careful. If you are studying on you own, without the benefit of others to help catch all the errors, then you will want another book.

A good book, better than many others I have used, but as otherreviews describe, it contains many blaring errors. Its text is muchmore readable than other books I have used, though.

I bought this as a college textbook and couldn't survive the class without it. It's very easy to understand, and Finale is by far the most user-friendly and versatle music notation program...I just wish it weren't so expensive.

As a teacher of electronic music and a Finale user since 1992, I have been looking for a good, well-written and reasonably priced text on Finale for my students, other than the online documentation (which is actually not so bad in of itself). This book contains some OK beginning exercises for students, but is not what I would expect in a quality textbook on Finale, and for a semester long course in music notation, you run out of topics rather quickly. Particularly, there is no addressing the more powerful aspects of Finale, including the versitale MIDI tool, among other advanced features. I flipped through the Rudolph/Leonard book from Berklee Press briefly, and that looked much more promising, but it is considerably more expensive. Granted, the title of the book does say "Primer", but at the same time, the concept of "Mastering" falls way short with this book.

This book spends too much time explaing computer operation (pull down menus, command keys) and not enough on Finale. Too often as it gets close to having some depth it says "but this is beyond the scope of this book, read your Finale manual." The one page index is worthless. The book does things like wastes 4 pages on a windows/mac keyboard comparison chart and yet does not show how to setup notating a drum kit. If this is your first piece of software, maybe it would be helpful, but if you think it gives insight and tricks beyond your manual, forget it. I feel cheated. I found some mistakes in the book and certainly the title "mastering" is an overstatement.

The Finale Primer is a waste. If you purchased Finale 98, the book that comes with it is nearly identical, so I now have virtually the same book twice. Also, it is very poorly indexed and cross-referenced, resulting in much frustration as I try to find assistance on various topics. You are much better off saving your money and using the original manual and HELP screens.

I began to read with great anticipation but was sorely disappointed. There were too many errors in the 2000 edition, which apparently had been revised in a hurry to catch up with the software upgrade. Many of the existing shortcuts were either inaccurate or, in the case of the new ones, omitted altogether. The author also geared much of his commentary towards Mac users and referred all unexplained problems back to the Final Manual. Very sketchy - and I still have not figured out how to set up the percussion so it sounds like the instruments I want. A complete waste of money.