I hesitate to write negative reviews because I always suspect that the errors I find are my own misunderstandings. In this case I felt COMPELLED to write one. I bought this book wanting it to be great and having high expectations based on the reviews I read. I doubt many of the reviewers OR the EDITORS read this book very closely. There are so many mistakes (small and large) and examples which flat out DON'T WORK, that the book has almost driven me mad. I've wasted HOURS trying to get things to work the way the authors described. The errata posted on this site lists maybe 1/4 of the errors. There is ONE posted review on Amazon.com which took notice of this, but all of the others seem to miss it completely. Kudos to Raymond Smith! (http://www.amazon.com/gp/product/customer-reviews/0596005792/sr=8-2/qid=1179328510/ref=cm_cr_dp_pt/104-6923608-7298356?ie=UTF8&n=283155&s=books&qid=1179328510&sr=8-2#customerReviews)
Two perfect examples (in case you want to save yourself a few hours of struggle):
1. The Invoice Finder tutorial on page 372 simply doesn't work using the "minimum amount" field as they describe. It will work using the date range criterion, but when you add the minimum amount match, it fails. I built a file following along with the text and thought it was MY file that was broken. Then I tried the files supplied with the Missing Manual "CD". The authors' files don't work either. They SEEM to work with the data already in them, but if you add an invoice, it doesn't work. And if you simply open the "options..." definition of the Total Due field on the "Invoices" table, then OK the dialog box, all the existing data fails as well. It must be some kind of indexing problem, but the fact that it slipped by the editors is almost impossible to believe.
2. Repeating Fields for Multiple Results on page 417 is totally wrong. The formula they supply will not work at all, and in fact, unless the "Price" field is a repeating field as well (which they don't mention at all), you can't do any calculations using the "Get(CalculationRepetitionNumber)" that will work the way they describe. Not to mention the fact that in the second mention of the calculation they call it "Get(CalculatedRepetitionNumber)" which is wrong and won't even take. The text suggests that you "test this calculation with a few numbers", but I doubt that any editor tried it. AND THIS IS LISTED IN A POWER USERS' CLINIC.
I don't know if this is an author problem or an editor problem, but either way, it is a REAL problem for readers.
What a disappointment and a waste of may hours... Don't listen to the majority of reviews on this book. They have clearly come from people who read it but were not actually trying to learn from the DOING the examples in the text. The book is written in a friendly easy style, but there are too many errors to make it valuable. And it's been out for TOO long for these things not to be listed in an available errata or supplement.
|
