Building Applications with Microsoft® Outlook® Version 2002 (Pro-Developer) [Paperback]

Criticism in other reviews focus on minor details seems to me to nitpick on irrelevant details, while ignoring the fact that Byrne exhaustively discusses Outlook programming with Visual Basic and VBA, including Outlook functionality and the use of the Outlook Object Model (and CDO as well as a little MAPI as relates to Outlook programming). The book is filled with relevant explanation and analysis (not just minimalist captions or code comments, or explaining the obvious).

For a book of this size and scope, a certain number of errors are inevitable. I'm surprised there are so few.

An absolute beginner with programming would probably find this book took too difficult. On the other hand, it's ideal for someone who is familiar with Visual Basic and wants to program Outlook. Byrne discusses the structure and implementation of Outlook (and CDO) methods, properties and objects in sufficient detail to be useful even to an advanced programmer who needs a good Outlook intro and reference with sample code.

Byrne admits in his introduction that he had a difficult time completing this book because of all the security restrictions that MS has placed into the Outlook object model. Clearly, it was a blow to many developers, Byrne included, when MS did this. But as Byrne concedes, MS really had no choice. Byrne discusses strategies for circumventing the security restrictions throughout his book. Byrne is a likeable guy: he's not arrogant, and it's clear that he knows his stuff.

There are a number of subtle and confusing points that must be understood when designing an Outlook application. One example is the concept of "one-off" forms. Do you store the form def in an organization's form library, the application's public folder, or do you send the form def with the item? Byrne does an admirable job in discussing the distinction, but it may take several readings to fully understand it, and the implications behind it. Because of the security restrictions, VBA code will not execute in an one-off form. So, pitfalls abound.

Contrary to what one reviewer has stated, the Outlook object model is discussed in minute detail. Unfortunately, you won't find it until you have gotten through hundreds and hundreds of pages of relatively introductory material, some of which is prone to repetition. That is one of the biggest weaknesses of this book: too much repetition in the early chapters. One example: we don't need to know how to publish a form more than once, but there are at least three step-by-step examples of how to do this.

The structure of the book is such that the early chapters are oriented toward beginners and the later chapters toward more advanced programmers. That is as it should be. But I have to agree with other reviewers who have criticized the beginning chapters of the book as being just too elementary, too repetitious, and too sophomoric (eg, that silly vacation request form).

Overall, I came away from this book feeling Byrne's enthusiam for the Outlook object model, as well as his acute disenchantment at the new security restrictions that have been built into Outlook. This book was published before .NET was finalized, so criticism that it doesn't contain .NET material is unfair. I agree that the book is way over-priced.