5 comments about Professional SQL Server 2005 Integration Services (Programmer to Programmer).

1. While this text does contain quite a bit of information about SSIS and its functionality, it does not do a good job of relating or building an overarching conceptual framework for understanding. Specifically, I appreciate a learning text that simultaneously teaches the "how to's" along with a vision of "why" things are done as they are. This latter consideration is extremely helpful when we leave the domain of canned examples and venture forth into the real world.
   
   I suspect that when a team of authors assembles a text, as in this case, we get the benefit of vertical expertise but miss out on the encapsulated/synthesized wisdom that a single author conveys as he/she walks us through a detailed technology tool.
   
   After 7 chapters in this text I switched to Microsoft Press': "SQL Server 2005 Integration Services, Step by Step" - for which I have written a more favorable Amazon review.



2. SSIS only supports scripting in VB. But whenever there's a custom component or any code outside the mandatory VB realm, the book only presents a C# example. Even the WROX website does not provide VB code. So if I want to code my custom data flow task, or follow their wmi example, I MUST know C#. I can follow along okay, but I don't like having to interpret/rewrite your code samples to be able to use them and extend upon them.
   
   The general information is good, but don't think this book will leave mold you into an SSIS Expert. I only bought this book because I first bought the WROX "expert" ssis book, which started by saying they assume you have substantial knowledge of ssis, such as provided by this book.
   
   All in all, the book is a decent introduction to SSIS. I didn't suffer from the 10 author continuity loss as others did. I just want my examples in VB, especially for a product that only speaks VB for many functions.



3. If you're needing an SSIS primer, this is a great place to start. There are definitely holes the "how to" part of some sections. However, you really get a good idea of what's possible in SSIS. If you want script specifics, you may need to search for it on MSDN or the web in general--but, at least you know what to look for.
   
   Buy this before you buy the Expert companion title if you're new to figuring out how things work in SSIS. I had several years of experience with DTS packages, and this book was a perfect start for me.



4. I originally intended to give this book two (2) stars, just because I was hacked off at the terrible index, but the content is worth at least three stars. The problem is locating the specific content you need.
   
   Example: User-defined package variables are often critical pieces of a SSIS package. Want to find out how to get/set package variable values from an Execute SQL Task? Well, you won't get anywhere trying to look up "Variables" in the index. Just when you think the text does not address this important issue, you browse the Execute SQL Task section and -- lo! -- there is an extended discussion on how to access package variables from SQL queries. But none of it is referenced by the "Variables" entry in the index.
   
   Brian Knight, by all accounts, is a good writer who knows his material, but any book that has ten (!) authors can't help but display a variety of writing styles and competencies. The book is adequate as a learning tool, but not as a reference. If the publisher had been in less of a hurry to get to market, Mr. Knight might have been allowed to take on fewer collaborators and produced a more coherent book. And a more complete index.



5. So far this book is great for basics. It gives a great overview of all the options you have to create a SSIS package. I had previously purchased the expert version because I had DTS experience and realized SSIS was totally different. So I bought the professional version and it's filled in a lot of gaps. It's also got nice tutorials at the end of the chapters that help you to create a basic SSIS package which is incredibly helpful for learning the new tools that are available.

5 comments about Patterns of Enterprise Application Architecture (The Addison-Wesley Signature Series).

1. As a newcomer to enterprise architecture this book educated me on possibilities for decisions to be made in designing an enterprise architect. It will also give you a language for describing existing characteristics of an existing enterprise application which may use some combination of the patterns describe in this book. The discussion of where to keep session state for a webapp was particularly helpful to me.



2. For me, this book is an invaluable reference for building business apps.
   
   Want help choosing a framework? Want some guidance for solving common business problems? These patterns help solve these kinds of problems.
   
   NOTE: I have tried to find other sources for these patterns, and I have only found Fowlers website, which is really only a summary and recommends purchasing the book.
   
   This book has examples in both Java and C#. You can certainly use these patterns in .NET.
   
   Under .NET you are not actually forced to use the Table Model. I think the purpose of this book is to help you realize this.
   
   There are frameworks for .NET that use the Domain Model and Data Mapper patterns, but you would never know this unless you were familiar with the patterns in this book.
   
   For me, reading this book didn't allow me to write new code, but it did allow me to understand my choice to use a particular framework/technique over another.



3. This is a must read book if you are a developer, architect or in anyway related to technology.



4. Even if you don't do "Enterprise Application" development, this book is a must have in your library. If you have been developing for more than a couple of years and you haven't seen 1/2 of the patterns in this book, then you are probably doing something wrong and this book could greatly help you.
   
   Even if you do know 1/2 or more of the patterns in this book it is a great reference to the details of these patterns. Unless you are a Sophomore Software Engineering Student I'd recommend this book over the GoF book. Gof is a must have too, but if you can only have one. Get this one!



5. This book is a complete beginner's handbook for enterprise patterns.
   
   1) The "Mapping to Relational Database Patterns" section discusses patterns that are completely intuitive. I recall logically coming to this conclusions when I started programming in Visual Basic in 99. Nothing new in this section.
   
   2) The "Concurrency" section is criminal in nature and assumes that the application runs on high-cost server. Process-per-session? Thread-per-request? Come on!! Has the author missed out on the Reactor, Proactor and Active Object patterns (he does reference ACE but only as a reference). These patterns have been recognized as not scalable in the late 90s.
   
   3)The distribution patterns are clearly incomplete and desire a lot of details.
   
   If you're just starting out,as a System Architect :-), you'll find this useful. Otherwise, use MSDN or ACE for enterprise patterns.

5 comments about Advanced Windows Debugging (The Addison-Wesley Microsoft Technology Series).

1. Have you ever tried to debug a problem in a productive environment? Do you know how hard this can be, especially when you are not allowed to install or use your full Visual Studio environment? Or did you ever try to debug a problem which only happens at the customer's side? This book shows you how to do all of this, and much more. It shows you, for example, how to create and use a memory dump and how to set up and use remote debugging.
   
   And this is a very concentrated book. It covers a very wide area of expertise. It is an indispensable companion for every real world programmer. It explains in detail some of the lesser-known areas of programming infrastructure, like stacks and heaps and the RPC (DCOM) infrastructure, the possible error symptoms and their analysis.
   
   Did you know about the powerful tools in the Debugging Tools for Windows package? This book begins with an introduction to these tools. It shows you how to set up and use them. It introduces you to the user-mode and kernel-mode debuggers, the Global Flags, the Application Verifier and many other tools. All of them are available for free. And you can easily give them to your customers or to the IT department of your productive environment.



2. The focus is on debugging using tools other than Visual Studio. There is still a lot of useful information about other tools, but if you want to learn how to debug with the Visual Studio debugger, this is not the book to get.



3. A very good hands on book with many gems of knowledge. It walks you through the processes of different debugging techniques with easy to follow screen shots. I definitely recommend this to anyone writing Windows OS dependent code and it is even a very good book to read even if you are a .Net or Java developer on the windows platform. Even if you consider yourself advanced in this area you will still find a few new tricks.



4. Chapters on debugging heap/stack corruptions are simply invaluable. Worth reading even if you think you know everything about those issues, this book will easily prove you wrong.



5. This book has completely smashed every possible expectation I had when I set out to read it.
   
   Let me put it simply. There comes a time in every software developers' life when he contemplates the age old question of, "If I were to be stranded on an island and I could bring only 3 things with me, what would they be?" Well, this would be one of the 3 items. (The other two would be Windows Internals by Russinovich and some other obvious classic like the Windows via C/C++ by Richter, or UNIX Network Programming by Stevens). This book is easily on the same playing field as such classics as those, and its only flaw is that it is not 1,000 pages because when a book like this comes along, you really just don't want it to end. There is so much useful information in here.
   
   The chapter on LPC debugging is worth the price of the book alone, as LPC is completely undocumented and you literally will not find this type of information anywhere else. Every single chapter in this book is filled with gems, and with the plethora of average books being released recently, it really took me by surprise to read such a well thought out book that hits all the right topics in all the right ways.
   
   That being said, it is advanced. Yes, I realize the title says it, but too many books come out with the word Advanced in the title that are merely Intermediate. You need some assembly language, you need to be comfortable with native code, you need to not be frightened at the thought of debugging something for which you have no source code. But for those that meet the pre-requisites, this is a must-have in every sense of the word for the serious developers' bookshelf.

5 comments about iPhone Open Application Development: Write Native Objective-C Applications for the iPhone.

1. As a programmer who creates interactive demos for visions of the future, it is very important for me to be on the bleeding edge of mobile and multimedia technologies. Such technologies include the release of Flash player 9.0.115.0 (with HD support), Flash Lite 3.0, Flash Media Server 3 (ActionScript has been key for me in its portability), and lately the iPhone open toolchain (due to the coolness factor of the iPhone).
   
   When it comes to the Mac platform, I've only just begun getting my hands dirty. I got my first Mac a year ago and was surprised with the ease in which I was able to get started with the toolchain from the instructions in this book. The setup was extremely easy, but the most benefit of this book comes from chapter 3, which describes UIKit, the framework which handles most of the UI elements on the iPhone. This chapter was incredibly descriptive and helped me to better visualize how my app is put together.
   
   For a programmer who needs to be able to get things done yesterday, this book really helped me earn a lot of brownie points at work. Coupled with the helpful nature of the author (who is available via IRC), I find this book an excellent resource.



2. I returned this book, since I bought it after Apple's iPhone SDK was released, I assumed that would be the topic of the book. This book is for the development of Jailbroken iPhones. I'm sure I would have learned quite a bit from reading this book, but I'm just more interested in using Apple's official SDK, since my iPhone is no longer Jailbroken and I don't plan on Jailbreaking again.



3. iPhone Open Application Development is meant for hard core developers.
   The writing style is very concise and to the point, not much BS. If you don't understand certain parts of the book, you can always Google.
   
   I'm from Java background, but picking up Objective-C and trying out some samples in the book do not seem to be super difficult for me. I also got the toolchain built successfully by following the steps in the book, although there was one error in the LLVMOBJDIR setting but can you find the solution in iphone dev google group.
   
   You don't need to wait for Apple's official SDK 2.0 release in order to build iphone applications. And the most important thing is: you can run your application on your iphone w/o bricking it (as comparing to what Apple's beta SDK will do to you). And it's totally FREE!
   
   Highly recommend this book to any serious iPhone/iPod touch developers.
   The samples in the book along can last for quite a long time.



4. If you are confused by the reviews here, you really need to go read the forum posts ( look for the "Customer Discussions" links below these reviews).
   
   
   Personally, I wouldn't do this - too geekish for me, and if I were going to get into it, I'd go the "official route". The author made a very good point about this in the forum:
   
   quote
   It clears up a lot of confusion if you look at the Apple SDK as the "AppStore SDK", rather than a form of official SDK. The "AppStore SDK" as it is today summarizes what Apple will probably allow you to do in official AppStore applications. What you can technically do hasn't changed - it's just what Apple will "allow" you to do if you want to get on AppStore.
   endquote
   
   So if your interest is developing your own apps that you either aren't selling or at least won't be selling through the official store, this is fine. I thought it was well written, and although I can't follow it fully , it seems to lead you into the subject well.
   
   I do harbor other feelings about this. While I think Apple is very smart in how they've opened this up while keeping it firmly under their control, I still think that Apple and the world would be better off it it were really open. In that respect, I applaud the author and hope that thousands of developers embrace this and force Apple to relinquish control.



5. Be warned this book is for unlocked iPhone application development only; not the official Apple iPhone SDK. If you are interested in hacking iPhones, this may be for you. But for most iPhone application developers, the material here will be of little use.

5 comments about Microsoft® Office SharePoint® Server 2007 Administrator's Companion.

1. If this companion where a living entity, I would kick it off my team.
   
   Having an O'Reilly safari account I read through it and was very disappointed in that it doesn't cover some of the basic functionality that might be expected from a companion.
   
   As for the hype, don't buy it to it!



2. The sheer amount of information presented in this volume is impressive in and of itself. The depth and quality of coverage into the many topics varies, and there's no one topic covered in totality, but this is the "one" book. English et al. nailed coverage across topics i.e. in scope and breadth. This is certainly not the book for beginners; there is a degree of basic SharePoint knowledge assumed, and you'll need to go elsewhere for deeper developer discussion (e.g. Pattison and Larson) or specifics on administration (various blogs). But if you're to make a career out of SharePoint 2007, you'll need most if not all of the information that's contained in this book. It's nice to have it in one reference.



3. This book is geared toward readers such as Web Developers, Information Management / Compliance Specialist, Administrators to name but a few. If you are a beginner to Sharepoint Server 2007, this book will be a most difficult read. The concepts and topics that are presented will have to be re-enforced with online research or the purchase of another book.
   
   To give an example.
   The book is composed of six sections, with the first three ( 663 pages in length ) being targeted towards administration and configuration. However, within this mix we have presentations on performance monitoring and MOM 2005, high level discussions on information security policies such as password and storage policies, data classification. We are introduced to advanced Enterprise topics such as the Business Data Catalogue and records compliance ( that is the Sarbanes Oxley Act etc. ). These discussions all assume prior expertise and should you be new to Sharepoint Server 2007 this will no doubt frustrate you. The Authors, in their quest to appeal to a wide variety of readers, cannot delve into the in-depth explanations, followed up by well worked out examples that a beginner to Sharepoint Server 2007 would require.
   
   Web Developers will tend to focus on Sections 5 and 6. While these sections do introduce Workflow Services, Webparts and products like Sharepoint Designer I found the overriding theme is again one of high level discussion and overviews. Expertise is assumed.
   
   Overall I would say that if you are coming from a background with some expertise in Sharepoint Server 2003 or you require a high level picture of the abundance of features that Sharepoint 2007 can bring to your organisation in addition to how it integrates with other server platforms, such as ISA 2006 for example, you will enjoy this book and the nuggets of useful information it provides. The writing style is not engaging; this book is not a joy to read but it will tell you what can be done with Sharepoint Server 2007, outline best practices and point you in the correct direction. The how-to part is very much left to yourself.
   
   If however, your goal in purchasing this book is an in-depth knowledge of the installation, administration and configuration of Sharepoint 2007 and you have no prior expertise with Sharepoint Server 2003 or indeed 2001, then you will gain little benefit from this book. You will find it difficult to read, difficult to digest and your understanding of Sharepoint 2007 will not improve. If anything, you may be discouraged from using Sharepoint Server 2007 which would be a shame as the product is in my opinion really good. Regards.



4. This book covers most of what an administrator needs to know, very acurate information. I use this book all the time for reference because you can't retain everything that's in this book, it's a great tool for studying for MS Exams.



5. Useful reference and the eBook (pdf) has been invaluable. Unfortunately, the pdf is locked which restricts copy/paste (which would be great for documentation). This booke is not a sit down and read from cover to cover, but a go to book for research/reference.

3 comments about Microsoft Office Outlook 2007 Inside Out.

1. This is a good all around guide. This is a book designed for outlook beginners. Also touches on some more advanced topics. This is not an all in 1 guide for outlook 2007 but summarizes many things well.



2. MS Office Outlook 2007 Inside Out easily maintains the high standard of usefulness of the Inside Out series. I found this volume very helpful when installing Outlook 2007.



3. The book is extra ordinary, easy to use and as detailed as you desire to go. In addition it offers a CD-ROM with an array of goodies. For me the print templates were of great value. I can highly recommend the title as you will find an answer for almost anything related to Outlook.

2 comments about GO! with Microsoft Office 2007 Introductory (Go! Series).

1. book was a good price, sold with the course disc, only the disc was for the 2003 course.



2. I purchased this book for my oldest daughter who is not familiar with computers. I had seen it as a textbook at our local community college. It has very easy step-by-step exercises & really shows all the ins & outs that Office 2007 has to offer.

5 comments about C# 3.0 Design Patterns.

1. I bought several copies of this book to teach my development team design patterns. I have a copy of and like the Head First design patterns book, but my guys wanted to learn some of the new C# 3.0 features and judging from the other reviews I thought this would be a decent book.
   
   Boy was I wrong. Do not trust the positive reviews. The examples and coresponding code samples are flat wrong. I don't mean code won't compile, I mean they don't teach the purpose of the design patterns or blatently defeat the pupose of them. I am only up to chapter 3 and I am having to create cheatsheets that show how the patter REALLY should work. If anyone is reading this and really wants to learn the design patterns, I would recommend the Head First or the original Gang of Four books. Beware, if you don't know design patterns and use this to learn you will be shooting yourself in the foot.



2. As with all books on patterns, I had high expectations from this book. I was really hoping that the author would have introduced new patterns utilizing new 3.0 language features that I have not yet thought of on my own, but was disappointed to see that the book is mostly another poorly written book on design patterns that happened to use C#.
   
   After realizing that the book was what it was, I was hoping that she would have done something a bit on the cutting-edge side of things by fusing new C# 3.0 language constructs and design patterns, but again, disappointed. The application of C# 3.0 features throughout the book seemed to be more of a showcase ("hey look what I can do") as opposed to practical or necessary.
   
   If you understand that this book is just another patterns book and doesn't introduce new patterns or really take advantage of new C# 3.0 language features, this book is ok. On a positive note, the book is a simple read. But if you're looking for a really solid book on patterns for the bookshelf, the gang of four patterns book (1994) is still the way to go.



3. This book was poor. The source code has errors. It does a poor job at explaining the issue a pattern is attempting to address. Made me very sleepy. If you want a good primer get "Heads Up Design Patterns", if you want more get the GOF book.



4. Lets face it design patterns are something that we have to have but at the same token are usually difficult to understand where it should be used and how to create it. With design patterns C# 3.0 By Judith Bishop we have a little more help.
   
   From structural patterns to Behavorial we can all feel a bit better in designing our tiers for robustness and making things just a slight more easier on ourselves. When i had to create a protected class for an application that i was working on. I had difficulty creating protecting it from instantiation with the guidance in this book i was able to complete the application in less time and focus on other areas of code that needed improvements. I also found use for the decorator pattern, while i will admit some patterns in the book seem like a lot of work to include in an application Bishop makes the case for each one and also describes situations where patterns may be become anti pattern for example using the Singleton pattern to hold static information as a global variable.
   
   Overall, the quality of this book is top notch (figures since it is a O'reily book) and offers many sections on how to enhance your coding practices to make best of your limited time and also of your program. The examples in the book are superb and offer a introduction to what i feel is one of the more complex ways of designing a program. It also has a fair bit of UML diagrams and is "decent" practical guide to also adhering to UML based designs.
   
   Something though i wish they had in this book were more samples, at times there seems to be decent coverage on some of the easier patterns (singleton) and not so much on the more convoluted patterns like Model View Controller. While she does try to create a balanced ground sometimes, i have to re-read the section because she gets to technical sometimes. I guess with time and over the years her thoughts should become more clear.
   
   - Mike



5. Overall, the book seemed pretty useful. Some of the patterns covered in the book are probably rarely used in the real world, but others are design patterns that we use as software developers pretty constantly without realizing it. Getting a formal definition of what those are, and all the different parts involved ... as well as when it is a good idea to use it or what other pattern might be a better fit really offers some value. It was a pretty short book, so I thought it was worth the investment of time to read it.

5 comments about Head First Software Development (Brain-Friendly Guides).

1. Head First Software Development is another home run from the Head First series. I have bougth the HTML/CSS, Design Patterns, Object-Oriented Analysis & Design, and now this book. These "Brain-Friendly Guides" are such wonderful learning tools packed with great information, and so much fun to read. Keep them coming!



2. The way this book is writen is just fantastic. Wonderful book to LEARN how to develop GOOD software.



3. I've been eyeballing the Head First books for a while, specifically the Java and Object-Oriented Analysis & Design. I don't program in Java and I think I understand OOP very well. Because of this, the Head First structure looks to offer a bit less structure - so a good "read as you can" book.
   
   I got this title in a raffle. I'm glad I did. It whetted my appetite for more Head First. Not so much for the content (Which I will review further down) but because it's almost like reading a comic book. Easy, entertaining and something my busy dizzy mind could readily grasp in small chunks. I will probably get another Head First book in the future. Probably more than one.
   
   As for the content of this book, it was well laid out and for someone new to the concepts of formal software design, it was nice to see all the little pieces come together. I did have a hard time with the Java specific environment, but I guess it would be a much larger book if they covered other systems. The steps were clear, some of them a smidge corny, but most of them logical.
   
   After having read this, I was inspired to put it to use. That's when it hit me. I can't see this working unless the entire development group reads the book - or they were all newbies. Well I can see it, just not in the places I've worked.



4. Although I was initially put off by the non-serious cover and gimmicky premise, I decided to trust to O'Reilly and give this book a try. That turned out to be a great decision!
   
   Be forewarned that the real title should be "Head First AGILE Software Development," so don't expect other methodologies, but it definitely delivers. Whether you're just beginning to take the plunge into agile development, or you've been sort of trying to do it for a while but don't have a real clear picture of your goal, this is a great book for you.
   
   However, if you've been developing agilely for a while, then what you'll find here isn't much more than a refresher course or reminder of how you should be doing things.



5. I first lend this book from collage developer an have read with great enthusiasms and finally ordered my own copy of this book.
   The book gives detailed information on how to developing software from scratch, taken you by hand and leading you de hole way step by step.
   With the different way to present the information en with lot of illustrations its newer a boring read.
   
   Anders Kjaer
   
   [...]

5 comments about FileMaker Pro 9: The Missing Manual.

1. It's been years since I used Filemaker, and then only as a database user...not the creator of the application. So when I set out to create a new FM database solution for a small private school I needed help! The tutorial provided with Filemaker9 is VERY basic and the application's "Help" tool is very thin. (I finally stopped clicking on it when search after search yielded no real help at all.)
   
   I picked up a copy of the Missing Manual hoping it would save my neck. I found that I already knew the material in the first half of the book, which was actually comforting. It was the second half where I found the help that I needed to make my FM solution do what I wanted it to do. The Missing Manual is well written by real humans...even with a bit of a sense of humor thrown in. And downloadable files on the Missingmanuals.com site make it easy to learn through hands-on exercises.
   
   I'm now rockin' & rollin' on my new database application! FileMaker is a powerful tool and the Missing Manual has helped me to unlock its secrets! A few dollars very well spent!



2. One of the first things that I noticed about "FileMaker Pro 9: The Missing Manual" is it's size. It's a big, heavy book, clocking in at 778 pages. But there is a good reason for this: This book covers a lot -- and I mean a LOT -- of ground. As such, it has something for everyone. From newcomers to veteran developers, you're bound to find something new here. So don't let it's size scare you away!
   
   Written by Geoff Coffey (of Six Fried Rice fame) and Susan Prosser (president of dbhq, a FileMaker certified consulting firm based in Gilbert, Arizona), FileMaker Pro 9: The Missing Manual is part of a series of books published by Pogue Press. Like other books in the series, it is very well written, and is presented in a way that allows a lot of information to be presented without overwhelming the reader.
   
   The book is divided into seven parts. Part One provides a good introduction to FileMaker Pro and is a good start for FileMaker newcomers. Part Two covers layouts, including all of the tools that are available to us in layout mode. Part Three dives into relational databases, with information on modeling, relationships, table occurrences, data tunneling, and more.
   
   Part Four deals with calculations, and does a good job of explaining topics that can be hard to grasp, including the Self function, the Let function, and variables. The "Power User Tip" in this section is one of the best examples that I've seen yet on how to put the Let and Self functions to good use. It shows how to use these functions, and a few others, to clean up and format a user-entered phone number.
   
   FileMaker users who have yet to automate their databases with scripts will find Part Five of FileMaker Pro 9: The Missing Manual especially useful. Everything from script basics and how to use ScriptMaker, to advanced scripting techniques, is covered. The information presented about script parameters is especially informative. Readers will learn how to pass multiple parameters to a script, as well as how to pass parameters to subscripts. Script variables, and error handling techniques, are also covered.
   
   Part Six covers FileMaker security and integration. Readers will learn how to use FileMaker's built-in security model to protect their databases. In terms of integrating Filemaker, this section explains how to share data in FileMaker databases with other systems, and vice versa. The authors do a great job of introducing what many believe to be one of the most compelling new FileMaker features: External SQL Sources (or "ESS"), which was introduced in FileMaker Pro 9. Rounding out Part Six are terrific explanations of some of the developer utilities that are only available in FileMaker Pro Advanced. Copying and pasting database structures, the script debugger, the data viewer, the database design report, tooltips, custom menus, and more are covered.
   
   And finally, Part Seven includes two helpful appendixes. Appendix A, "Getting Help," offers a good review of other places that developers and users can turn to when they run into trouble. Appendix B provides a list of FileMaker Error Codes.
   
   At a list price of $34.99, FileMaker Pro 9: The Missing Manual is a smart, affordable investment for any FileMaker user or developer. Reading the book is like taking a crash course in FileMaker Pro development. Read it, and your FileMaker skills are sure to benefit!



3. Pros:
   
   - The writing style is accessible and easy to understand
   - You can download the database examples used in the book.
   - It's the best FileMaker Pro 9 book I've seen.
   
   Cons:
   
   - Like a lot of computer books out there, this one is unnecessarily wordy. The publisher said, "I need a 750-page book," and the author complied.
   
   -And you gotta read ALL of it (especially beginners), because important information is distributed like buried treasure.
   
   - The wordiness and lack of consistent structure makes it easy to get lost. Let me give you an example:
   
   This is my first stab at FileMaker Pro. The first chapter shows you how to find records. It starts out nicely with bolded text showing the steps to perform a find. Then it gets wordy. And then it shows a few figures of what you will see. Huge paragraphs of smaller, italicized text accompany the figures.
   
   I skipped the figures and went on. Suddenly, I couldn't access most of my database entries. I went back to Browse mode, like the book told me to do, and still couldn't see them.
   
   Finally, after much digging, I found the crucial step I had missed, buried in the smaller, italicized text of the gargantuan paragraph accompanying Figure 1-17. Inconsistencies like this make the book a tough slog.
   
   I just brushed up on my Access 2003 (I haven't used it in 7 years) with one of those procedure-based illustrated books. It took me 3 hours to get through the 250-page book. It took me about an hour to get through chapter 1 (27 pages) of this book.
   
   
   I recommend downloading the examples from their website (I doubt you got a CD-ROM with your book). See the Missing CD-ROM link on this book's web page.



4. This is a thorough review of how to set up various database features of the Filemaker system. Like many such manuals I have had in the past, I found myself reading and re-reading instructions feeling there must be clearer, better ways to instruct someone on the various procedures of this fine database software. Nevertheless this reader got over some difficult spots in setting up his database and gives the book a positive review...



5. FileMaker Pro 9 is one of the most intuitive and user-friendly database programs available. But, as with all database programs, it is capable of so much that it is practically impossible for the typical user to deduce all of its functionality simply by searching the program's multiple menus.
   
   Enter FileMaker Pro 9: The Missing Manual - another edition of the Missing Manual series designed to enlighten non-technical persons on highly technical subjects.
   
   The main selling point of the series is that it is very simple to read. O'Reilly's writers are also extremely knowledgeable in the subject area. Geoff Coffey, has been a FileMaker Pro trainer and consultant for over 10 years. Susan Prosser is also a FileMaker consultant, as well as a database program creator. Along with the Missing Manual creative team, these authors impart their wealth of knowledge in a way that anyone could understand. And since they aren't part of FileMaker, Inc., they aren't afraid to point out any of the software's problems.
   
   When comparing FileMaker Pro 9: The Missing Manual to the user's guide supplied in the software's box, several differences are notable. The biggest is size: the Missing Manual is wider, taller, and much thicker. So if you just need a quick introduction to the program, this book might not be what you need. Learning a program as extensive as FileMaker Pro takes time, and delving through the Missing Manual is going to take a lot of it. But if you want to get the most out of FileMaker Pro, then the user's guide just isn't enough. The Missing Manual also notably uses less complicated language, has more example images, and presents a intuitive flow of information than the user's guide.
   
   One of the biggest benefits of FileMaker Pro 9: The Missing Manual is the online support. Armed with just the software and user's guide, you have to learn from scratch. The Missing Manual, on the other hand, offers several pre-built databases that it guides you through. This not only gives you an example to work with while learning, but also shows you various ways that your final databases could be built and organized.
   
   The indexing is also much more detailed in the Missing Manual. So if you ever forget how to work a specific function of the program, the answer is a quick look-up away, though there are several instances in which the index reference the wrong section of the book (but the right page number). This is probably due to a late chapter reorganization before publishing.
   
   While the current Missing Manual is well supported with examples, it does not, as yet, support any new software updates being offered by FileMaker, Inc.. In other words, the book is written for the FileMaker Pro 9 program right out of the box. If the company puts out any updates that alter the software, then you need to do your own research to figure out the changes. Also, when FileMaker Pro 10 becomes available, there is no smaller Missing Manual explaining just those changes - you'll need to pick up a new edition. So if you're not new to the FileMaker Pro software, these manuals might be more than you need.
   
   I found FileMaker Pro 9: The Missing Manual to be perfect for someone just starting to work with database programs. It's step-by-step process will have you building your first personal or professional database in no time!