Recommended in "A Basic List of Recommended Books and Journals for Support of Clinical Dentistry in a Nondental Library" in Bulletin Of the Medical Library Association, July 1997.

I've not read this book. But Marty is a good guy and y'all should all buy his book. I hear he's about to publish a biography on Michael Polanyi. I can't wait to read that one too!

This book is a must for anyone preparting for their Physics Candidacy exam. The advanced graduate students traditionally pass this book down to the incoming graduate students. Nice challenging probelms with clear solutions. Good luck studying for the exams!

As one of the poets featured in Will Work for Peace, one might expect me to be a bit biased, but nothing could be farther from the truth. Most poets work in a virtual vacuum, only tenuously connected to each other by the occasional workshop or shared membership in a 'poetry society'. When Brett Axel first approached me for a submission to an anthology he was considering, the names Marge Piercy, Lyn Lifshin, Moshe Bennaroch and so many others were abstractions to me as a fledgling poet. I knew these tremendous writers were 'out there' somewhere, beating down doors with their words and keeping a struggling artform alive. But to think that someday I would ever share a credit with these dynamic modern poets would be a pipe dream at best. It is through the sincere efforts of Brett Axel that many newer voices like mine have an extraordinary opportunity to appear with Pulitzer Prize winners and other poetic heavyweights. By way of an honest review, however, I will say this- not everything in this book will be to your particular liking. I myself came across some works that did not move me in the way the author may have intended. Some imagery can be raw and visceral, using shock value in place of craft at times. But to ignore those voices would be an even more shocking turn of events, so praise be to the editor for not sacrificing his vision to a senseless conformity. As Pete Seeger so aptly put it in his quote, trying to read all these poems at one time would be like trying 'to swallow Manhattan whole'. I say to you- buy this book, read this book, but understand that it's what you do after reading this book that will ultimately define who you could be. Poetry is alive and well, and lives in the blunt pages of Will Work for Peace.

Just amazing start to finish! I like the disregard for fame used in putting the book together. That great poems got in even if they were writtenby nobodys. Look at Roger Bonair-Agard's poem on page 74. Shortly after Will Work For Peace came out he won Slam Nationals, becoming Slam Champion of 1999, which will be getting him lots of offers. But Zeropanik Press didn't need to be told he was good by an award. They could tell by his writing! Good for them and good for all of us because Will Work For Peace is a literary milestone. It's a new standard for all future anthology editors to try to live up to. Thumbs up to Brett Axel and Thumbs up to Zeropanik Press for their guts and integrty.

Brett Axel visited my Church and I bought a copy of Will Work For Peace from him, not for poetry, but because I care about working for peace. I started reading through it thinking It'd just go on my shelf and that'd be the end of it, but the book grabbed me and kept me rivited. If I had known that poetry was this alive I'd have been into poetry. I've been reading some of the poems to my friends who also didn't think poetry was important and they are saying the same thing. Fantastic! There's no way to get through this book without having your old mindsets challenged. It's funny, powerful, sad, and uplifting. A book that deserves to be read by everyone. A book that really can make the world a better place!

This book omits several important events in U. S. History up to 1865. But is sufficient for introductory classes in U. S. History. While it does a sufficient job as a survey source, it is not recommended for an in-depth study of any period in U. S. History. Further, Roark seems to emphasize some events that seem less important to U. S. History.

This book is very well written, quite long, though

This book is oversimplified and leaves out important details dive students need to know in order to fully enjoy scuba diving while maximizing safety. This is just a hype book to sell the training agency who sponsored it and their poorly structured courses. Many superior books on this site. Save your money on this one.

We bought this for general information, expecting a simplified guide but found it to be very informative and interesting. Great pictures and notes, very easy to read, even for my 11 year old who can't wait to get certified. The cd-rom that comes with it is full of information, a quick PADI course, video clips, and it is worth the price of the book alone! a great buy!

This book is put together and presented in such a way as not to discourage anybody who has thought about learning to dive from doing so. There are a lot of books out there that are still influnced by training agencies that still think all divers should be taught like they are Navy Seals. It was refreshing to find a book that is accuarte and promotes diving for what it really is a fun, non-competitive, family sport. I have been involved in the dive industruy for over 20 years and diving for over 30 years and I highly recommend this book for anybody that has thought of giving Scuba diving a try.

This book has more errors than should ever be allowed in a professional product. There are typo's in both text and examples. The CD does not contain the source code from the book and I vote this the worst source ever of any computer based information I have found to date. It has left me very unsure of the publishers (QUE) standards and I may never purchase another QUE book again. I simply do not trust them. Spend your hard earned money on a different choice

"Special Edition Using Java, Second Edition" is an excellent reference to JDK 1.0.2. However, today (April 15), only a month and a half after being billed as "Computer Programming Expert Editor's Recommended Book, 03/01/97", it is a dated reference and the cover claims of JDK 1.1 coverage fall short--they are preliminary and peripheral to primary Java programming topics. For example, there is no coverage of the major changes in the Java event model of JDK 1.1, which permeate almost every application. I recommend waiting for better JDK 1.1 coverage, hopefully in Joseph Weber's new version, "Special Edition Using Java 1.1" which has not yet been released, but for which Amazon is taking orders today

This book is nothing if not large. This was QUEs attempt to capture the entire spectrum of JAVA and make it easy to understand (a task that they accomplished) but then the standards changed again. This is still a great book for learning Java; but, you will have to move on to other resources for news on the updates

Well presented, nice design but too elementary for researchers and people wanting to know a "real introduction" to aquaculture. Lacks of minimal technical details such as longlines or rafts design.

Having worked with Microsoft BASIC since "Basica" aka GW-Basic and QuickBASIC, I've had a chance to look at a **lot** of books about the language that's grown into Visual BASIC. Hands-down Ekedahl & Newman is one of the worst I've seen.

It's incomplete! When discussing substring splicing it covers the MID function but completely ignores the complementary RIGHT and LEFT functions. Yes, you can use MID to perform a RIGHT or LEFT slice, but when you're writing self-documenting code it's better to have all three functions available for the sake of clarity. (Update your code six months from now, and you'll be GLAD you used self-documenting techniques!)

It rambles! Information that should be in a sidebar or appendix, or that should be in a list are placed in long drawn-out paragraphs in the main text. Typical paragraph: "The Database object contains a reference to several other collections and objects. For example, each Database object contains a reference to the Recordsets collection. This collection contains a reference to zero or more Recordset objects representing the open Recordsets in the database. One recordset object exists for each open recordset in the database. You can open several Recordsets at the same time." (page 387 paragraph 3). Note the inconsistent capitalization on "Recordsets" and the ongoing repetition of one concept. This information would make just as much sense -- maybe more so! -- as a "bulleted list" in a sidebar. Clarity is not the strong suit for these authors.

Inadequate illustrations! Figure 8-15 on page 416 is the most ambitious illustration in the book, consisting of long horizontal boxes stacked atop each other. These boxes shrink to the right as you read down from the top, and they are all attached with a line. Other illustrations in the text use the same horizontal-box technique only with fewer boxes, which helps drive home the point that the authors may not know HOW to properly show relationships between functions and objects. (A look at the documentation from the Microsoft Developers Network shows the authors lifted the concept from Microsoft -- and sometimes the exact images -- just to have some sort of illustration. And no, they don't acknowledge Microsoft as the source of their images).

There is no succinct "language reference" anywhere in the appendices, a shocking lapse that should be corrected.

In a classroom setting, there was a lot of grumbling and complaints about the shortcomings of the text, followed by a significant dropout rate -- close to 50%. The few who stuck with it began purchasing supplemental books, referring to prior texts, scouring the Internet, and gleaning what they could from the MSDN CD-ROM.

If you're considering teaching a Visual BASIC class, give this book a pass. If you're going to take a Visual BASIC class, make certain you've got a good instructor to overcome the weaknesses of the text. And if you're just looking to improve your programming skills on a self-study basis, this is not the book for you.

I've programmed with Fortran and C, work with HTML, ASP (VBScript) and COM (Visual FoxPro), and have read a couple of programming books. This one is the first book that made it to my "Do Not Recommend" list.

I grew very tired of reading from the book. The reasons being:

1. To understand something I had to read a chapter right from the beginning to the very end, because it's using a very specific case to work its way throughout an entire chapter each time. I flipped back 5-15 pages at a time once I lost track of my reading.

2. This book does not give a good break point to let me pause and let a concept sink in my memory before proceeding with the next.

3. This book cannot, at any rate, be used as a handy reference book.

Writing style aside, the format is also terrible. It's probably fine to see black (font) and blue (boxes) in a book. However, this book prints the font so that it looks almost bolded. The paper it's using feels like cheap inkjet printer paper.

This book does have VBs intermediate-advanced stuffs such as class programming, MDI, and programming with databases (no ADO, though). If you have some VB experience, proceed with extreme care if you still want to use this book. If you're an absolute VB beginner, this book is not for you! Use David Schneider's book instead.

I've been lecturing VB for a while and I've been through various different books and I must say this is probably the best I've ever come accross. Dietel is excellent for reference but useless for "studying from", while most of the other books are "filling in the blanks" and students don't actually get to understand what an object is and what data driven is concepts are.

Sure this book has it's downside but untill I find something better it's "Tops" with me.

...This book was required for a VB .Net programming class I took at a local College. Out of 25 people no one found the book helpful in any area of learning programming. I even talked with some friends in other VB classes that were using the same book and their classmates responses were the same as ours. By midway through the quarter the instructor had all but abandoned using the book as a reference for the class. Instead of being called comprehensive it should have been called incomprehensible!

The Author's idea of programming examples is to show just a couple lines of code instead of how the code would be used in a program. The practice exercises call for you to use the author's prewritten code (which you have to download) and alter a couple lines of code to accomplish your task. This is not programming...

Most of the subjects that were covered were presented in such a poor method that the reader is left more confused after reading the topic than before. The book was espicially bad on Printing, Collections, Classes, and Load/Save to/from a file.

When you try to recreate a program using the author's code and making changes that you are instructed to perform about a third of the time the program will fail and the book provides such poor information that you can not troubleshoot the problem....

This book was used in our introductory VB.Net class. My fellow students and I were not happy with this book.

Problems with the book:

1) A programming concept is explained one way and then later used in a different way. For instance, the authors use "controlchars.crlf" to insert a carriage return/line feed. Later the author uses "crlf" to accomplish the same thing. The author fails to tell us that to do this, the programmer must
type "Imports Microsoft.VisualBasic.ControlChars" at the top of the file. Doing a task in 2 different ways without explaining the necessary steps leaves students confused, frustrated, and wary of using a Course.com book again.

2) The author's code doesn't always work properly. Chapter 7's exercise 1 is an example of this.

3) Exercises that are designed to teach a simple concept are often so overly complex that the reader doesn't learn the simple concept at all. Exercise 1 in chapter 7 is one example of this. It tries to teach how to read data from a file and then perform a mathematical calculation on the accumulated data. The data that the authors have the reader import into their program is so large that it is cumbersome for the reader to check if the program is working correctly. This exercise needed to be scaled back; instead of reading in hundreds of numbers and then averaging them, how about merely reading in 2 or 3 numbers so the beginner programmer can easily tell if his program is working correctly? Apparently the authors had trouble coding this too, since their solution did not work properly.

4) There are numerous "attention to detail" mistakes; a programming book cannot afford to have these.

5) There is no errata on their web site.

When I asked the publisher for a list of corrections for the book, they said they had none and offered to pay me to quality-check the book for them. A quality-check should have been done long before it was ever published. This book has the feel of one that was rushed out the door to be one of the first introductory VB.Net books on the market.

I have been a Visual Basic 6.0 developer for the last two years and decided to upgrade my skills to .NET I found this book very helpful and full of valuable examples and tutorials. The basics of .NET environment are explained well in detail before the actual programming is started and that leaves quite a bit of margin for the readers to fully understand the environment before wetting their hands with code. Topics such as ADO.NET and ASP.NET are also explained in detail. To my surprise this time there is a complete new topic for Crystal Reports and its features, which makes the book an all in one resource. I would recommend this book to all the beginners and skilled VB developers as well. Thanks !!