Contact Me, Please!

I ran across an online review of one of my books the other day. The author was mainly complimentary, but said he couldn’t contact me using e-mail and found that he felt alone in using my book. He obviously had unsolved questions and felt that he had been left alone to solve them by himself. Of all of the complaints I receive about my books, not being able to contact me for help is the one that hurts worst.

I want you to be able to contact me. In fact, I check several times a day, five days a week (Monday through Friday) for reader e-mail and try my best to provide same day support. The only exception is when I’m out of the office on vacation (I’m striving to provide an automated message to let you know when I expect to return to answer your question). Even then, the first day back from vacation is spent answering reader e-mail. Your comments, questions, and general observations are incredibly important to me. Just in case you haven’t seen it in the book, my e-mail address is:

John@JohnMuellerBooks.com

If you purchase one of my books, you’ll see my e-mail address in at least two places: About the Author and the last chapter of the book as a bare minimum. I try to make it a point to mention my e-mail address five or six times in the book. In at least some cases, you’ll also find my e-mail address on the back cover.

Despite my best efforts, you may find it hard to reach me. If you can’t reach me for whatever reason, contact the publisher. Every publisher I work with has a Web site with a contact page. Normally, the publisher supports a forum in addition to an e-mail address (plus other contact methods that vary by publisher). If you contact the publisher, you can be sure that the publisher will contact me. The publisher knows it’s in its best interest to send any reader queries my way as quickly as possible.

At this point in time, I want to wipe out the “I couldn’t contact the author” complaint from the face of the earth. If you have anything to say about one of my books, don’t be afraid to contact me and say whatever is on your mind. You may be surprised to find that I care deeply about your needs and want to be sure you get the best possible use from my books.

That said, there are some people who try to take advantage of me. I won’t provide free consulting and no, I really am not a marriage prospect (I’ve been happily married for 31 years now). I truly don’t have time to debug your personal project, no matter how much it might interest me (and believe me, you readers have come up with some truly amazing projects over the years). However, if you have any question about my book, the source code, additional materials, or anything of that sort, please contact me, rather than assume I won’t treat you right.

Now, here’s an opportunity to tell me how to improve my books. If there is some other place that you’d like to see my e-mail address, tell me about it. I truly want to hear from you. Let me know where it would help to see my e-mail address so that you can contact me about my books whenever you want. I’ll be waiting to hear from you at John@JohnMuellerBooks.com.

 

Review of ADO.NET 4 Step by Step

Microsoft has created a plethora of database technologies over the years. The managed form of ActiveX Data Objects (ADO) is just another in a long series of ways to access data from within an application. Because some older technologies, such as Open DataBase Connectivity (ODBC), are so entrenched, there isn’t any way that a single book can tell you everything there is to know about working with databases from a Microsoft perspective. When you add in all of the potential database products (SQL Server, MySQL, AskSAM, Oracle, DB2, and many, many others), the task becomes impossible. So, when I reviewed this book (supplied to me by the publisher), I didn’t consider completeness from the perspective of providing a single source solution to database management. In fact, given 25 years of experience, I feel that such a book is impossible to write—at least as a single useable volume. When shopping for a database management book, be sure you look for a book that covers both the required access technology (such as ODBC, ADO, or ADO.NET) and the database manager (such as SQL Server or MySQL) that you need for your project.

Tim Patrick has written ADO.NET 4 Step by Step with ADO.NET and SQL Server in mind. In fact, the book is incredibly focused and I applaud the author’s single minded devotion to this combination of technology and product. Other database books I’ve read just don’t seem to get the idea that watering down the message won’t work. While it might be possible to include multiple products in a book, trying to cover multiple technologies seldom works because there is too much to discuss and, even if the author successfully writes about each technology in an unbiased way, the reader tends to become confused. So the first thing you must know about this book is that it’s strictly about ADO.NET and SQL Servertry another book if you need any other combination.

This is the second Step by Step book that I’ve reviewed (see Review of HTML5 Step by Step for details of the other review). As with that other book, this book is heavy on hands on involvement and light on theory, which is just fine because many people learn better using hands on tasks. However, database management is a more complex task than creating a Web page because you have data integrity rules and other issues to consider that simply don’t come into play when working with a Web site. (To be fair, Chapter 12 does discuss data integrity, but mainly from a hands on perspectiveyou end up understanding how, but not what, why, or when.) I mention this because the hands on approach in this book does help you create applications fast, but it doesn’t provide you with everything you need to know to create good applications. For example, the discussion of ADO.NET components consumes a scant two pages. Database normalization is covered in a two paragraph sidebar in Chapter 2. The author is cramming a huge amount of theory in an incredibly small space and glossing over a lot of details. I would have liked to have seen some notes, tips, or sidebars with online resources as a minimum so the reader could fill in the missing theoretical details later.

The best part about this book is the activity. I was able to create a basic application in less than an hourfar faster than any other book I can remember using, even my own books. By the time you reach the end of Chapter 1 (about 15 pages), you’ve already learned how to create a connection to your data. Chapter 2 has you creating tables using several different techniques.

I loved the quick references at the end of each chapter. They act as a quick method of ensuring you got all of the details out of each chapter. If you read the entire chapter, you can go back to the quick reference later as a reminder of the things you learned.

Patrick provides a relatively good discussion of every aspect of managing the database and the information it contains using both C# and Visual Basic examples. Support for both languages is a good addition to the book. In addition, the support isn’t sporadic as it is in many books that favor one language or the otheryou’ll find most information discussed equally in both languages so neither language feels like a second class citizen.

Chapter 8 does discuss external connectivity, but it feels like Patrick is discussing the topic from the perspective of the developer who normally uses ADO.NET exclusively, which is absolutely correct for this book. You’ll discover how to interact with OLE DB and ODBC data sources. Unfortunately, as with many other areas of the book, the author digs right into using the connections without providing any theory whatsoever. This is another area where it would have been nice to have resources provided so that the confused reader could learn more. Still, everything works as promised, so there is something to be said for that. Many readers don’t want to know how it works, they simply want to know how to do something black box style and this chapter fits in perfectly with that mindset.

For me, the highlight of the book was Chapter 16. In this chapter, the author cuts through all of the usual garbage associated with objects and shows the bare essentials to use technologies such as LINQ. This is possibly the shortest, yet best conceived, coverage of the topic that I’ve seen anywhere. Again, you’ll find yourself lacking theoretical details, but the how discussed in an elegant way that will enable most readers to make use of these newer technologies in an incredibly short time. In fact, Part IV of the book goes on to cover LINQ in detail. I’m convinced that LINQ will eventually become the data query technique of choice because it’s relatively easy to understand, requires little code, and generally produces optimized results with little effort on the part of the developer. Obviously, the author agrees with me on this matter.

Overall, ADO.NET 4 Step by Step is a fantastic book for teaching you the “how” of database management using SQL Server and ADO.NET. In fact, you’ll learn how to perform many tasks that other tomes simply leave out. However, if you want to know why you’re doing something, when to do it, or understand the theory behind a task, you’ll need another book. I recommend this book to anyone who wants to get started quickly. You can always obtain a theoretical book to fill the gaps in your knowledge and you experience programming scenarios you don’t understand. The best addition the author could make to a next edition is some online sources to help the confused reader. Writing a database management book is tough, but it’s important to recognize that there are limits to what you can do and provide the reader with help in overcoming those limitations.

 

Review of HTML5 Step by Step

Microsoft has thrown developers yet another curve—Windows 8 will rely on HTML5 and JavaScript for a programming interface. The revelation has many developers horrified. For me, it means updating my HTML and JavaScript skills, which was one motivation for reading the book reviewed in today’s post. HTML5 Step by Step, written by Faithe Wempen, provides a quick method of getting up to speed on HTML5.

This book is designed to aid anyone who wants to know how to work with HTML5, which means that it starts out extremely simple. The book avoids the ever popular Hello World example, but the example it does provide is small and easily understood. The chapters don’t remain simple, however, so even if you have some experience with HTML, you can use this book to update your skills. You’ll likely want to start around Chapter 3 if you are experienced and skim through the material until you come to something unfamiliar, which could happen relatively fast given the changes in HTML5.

HTML5 Step by Step is light on theory and reference information, but heavy with hands on experiences. It relies on using Notepad as an editor, which may seem like an odd choice, until you read the “Why Learn HTML in Notepad?” section of the Introduction. The author’s reasoning is akin to the same reasoning I would use, which is to make sure that the reader types everything and understands why a particular element is required. If you really want to get the most out of this book, you have to do the exercises in Notepad as the author suggests. Otherwise, I guarantee you’ll miss out on something important. Faithe has made a great choice of teaching aids in this case.

Chapter 1 is most definitely designed for the rank novice. It even shows how to set up the examples directory as a favorite in Notepad. However, unlike many books, the rank novice should read the book’s Introduction because Faithe does provide some needed information there, such as the “Understanding HTML Tags” section.

Chapter 2 gets the reader started with some structural elements. Faithe covers everything that the reader is likely to need for a typical starter Web page. I wish that the chapter had covered <meta> tags in a little more detail, or at least provided a table listing them, but this book does have an emphasis on hands on exercises, so the omission isn’t a glaring one. As an alternative to including the information, an update could provide a URL that lists the tags so the reader knows where to go for additional information.

By Chapter 3, the reader is formatting text and starting to make the sample site look pretty. I really thought Faithe did a nice job of moving the reader along at a fast, but manageable pace. She shows the reader how to make effective use of tag combinations, such as the <kbd> (keyboard) and <b> (bold) tags.

There is the smallest amount of reference information in some chapters. For example, Chapter 4 contains a table on page 50 showing the list attributes. These references are very small and quite helpful, but the reader should understand that the emphasis is on doing something and that the reference material may not be complete. For example, the special symbols table on page 56 is missing the em dash, which is something most people use.

The book progresses at a reasonable pace. Never did I find myself rushed. The examples all seem to work fine and I didn’t find missing steps in the procedures. The author uses an adequate number of graphics so that the reader doesn’t get lost. I liked the fact that every exercise ends with a cleanup section and a list of the major points that the reader should have gotten from the exercise.

Readers who are only interested in new tags will need to wait until Chapter 9 to see one. The <figure> tag makes an appearance on page 141. However, even some professionals didn’t use all of the HTML4 tags and it really does pay to start at Chapter 3 and look for something you don’t recognize. It may surprise you to find that an earlier chapter contains a somewhat new (but not new to HTML5 tag) that you’ve passed by.

There are a few nits to pick with this book. The first is that the author places the accessibility information in an appendix where almost no one is going to read it. The information should have appeared as part of the rest of the book as appropriate. In addition, the author misses the big point that most people today have some sort of special need addressed by accessibility aids. The number of people who are colorblind alone is 8 percent of the male population and 0.5 percent of the female population. This book is unlikely to help you create a truly accessible sitenot that this is the reason you’re buying the book.

The second is that Appendix C doesn’t really help very much with the additions and subtractions for HTML5. For example, Appendix C doesn’t tell you about the new <aside> tag. If you want a quick list of the new tags, check out the www.w3schools.com HTML5 New Elements page. (I checked the missing <aside> tag against a number of other sites, such as About.com.) The point is that Appendix C won’t give you the complete picture. Again, this isn’t one of the selling points of the book, but the list should have been complete.

The third is that there isn’t really enough information about why something is done or why it changedsimply that it must be done or that it did change. The reader probably doesn’t want a full blown history of the change, but the why of something can make understanding and, more importantly, remembering a concept easier. Still, this particular nit is minor since the purpose of the book is to get you started with HTML5 quickly and not to explore it at a theoretical level.

Overall, HTML5 Step by Step is a great book for the novice who wants to learn how to create Web pages. It’s also an acceptable book for someone who’s experienced with HTML coding, but wants to get up-to-date on the HTML5 changes quickly. This book is definitely designed for someone who wants to do something, rather than simply read about it. If you don’t perform the exercises, you won’t get much out of the book.

 

Review of Creative Close-Ups

You may have noticed that I use quite a few photographs in my blog entries. Some of these photographs look nice (they aren’t art by any means) and some of themwell, they didn’t quite work out as I hoped they would. Over the years I’ve grappled with unwanted shadows and close-ups that aren’t quite close enough. Focus is also a problem and fuzzy pictures never convey what you want when it comes to factual posts of the sort I create. I was recently talking with Harold Davis about my photographic ventures and he graciously offered me a copy of Creative Close-Ups. As expected, this is a self-help book for people who want to create better close-up photography, which is the sort found most often in my blog posts.

The one thing that will strike you immediately about this book is that Harold is quite talented and is possibly wasting him time writing books, but I’m extremely happy that he did. The book contains page-after-page of striking images. Some of them have been Photoshopped, something that Harold readily admits and even recommends to an extent. Because I’m looking more for better real world shots and not necessarily art, I’ll very likely not Photoshop anything on my blog from an artistic perspective (I could very well use Photoshop to enhance images to make them better convey the information I want), but the book also pointed out the usefulness of creative croppinga technique I intend to employ from now on.

 

I’ll always tell you if I’ve modified a picture in some way. Otherwise, you can be sure that the picture you’re seeing on the blog is the picture as it came from the camera. I know that there is a certain amount of discussion about this topic and plan to be up front about any modifications or twiddling I perform.

Harold has convinced me that using a tripod isn’t quite the waste of time I thought it might be. The discussion starting on page 64 will probably change your mind too. There are few sections of the book that provide a purely artistic view of a topic, but you won’t find many. Instead, Harold tries to provide good solid reasons for doing things a certain way and then backs them up with stunning pictures. In fact, there isn’t a single photograph in the book where Harold has kept the technique secrethe exposes every technique for your learning pleasure. Where there are multiple ways to accomplish the task, you’ll find them listed, along with any pros or cons of that particular technique.

I found the discussion of equipment helpful in many cases. For example, in page 60 you’ll find a tip about the Lensebaby 0.42X Super Wide Angle accessory lens. However, the text isn’t formatted differently (as a Tip or a Note found in other books), so finding the information later isn’t as easy as it could be. In addition, there isn’t any picture of the lens taken apart so that I can see what he’s talking about. The information is probably quite helpful, but it’s less useful than it could be due to a lack of pictorial backup.

Overall, the book is more focused on technique, than on how to apply the techniquethe discussions of equipment left me scratching my head and I ended up researching the information on my own online. (Harold also kindly answered my e-mail queries.) Admittedly, there is a short list of URLs on page 234, but you won’t find a resource for every piece of equipment listed in the book. Creative Close-Ups lacks pictures of any of the equipment, so someone like me has no idea of what these devices look like. If I were to go to a store, I’d be completely lost. It would also be nice to know if there are places online to buy equipment where I won’t be cheated since the nearest camera shop is in Milwaukee (170 miles away). So, this book will tell you how to do something, but not provide you much in the way of describing the means to accomplish the task.

That said, there are many sections that make the book worth the purchase price (if the amazing photography and associated setup instructions isn’t reason enough). The section on focusing on page 68 is especially insightful. In fact, the tips on page 70 are precisely what I need to do a better job with my own photography.

This book provides me with plenty of room to grow. The discussion of focus stacking starting on page 124 will require plenty of work on my part and I may never master the technique in the same way that Harold obviously has. Still, the discussion gives me some ideas and I hope that I’ll be able to use the technique in my blog.

Creative Close-Ups provides inspiration, food for creative thought, and lots of technique. I don’t think that a complete novice will be able to use the book because Harold doesn’t explain many terms such as ISO and what an f-stop is, making notations such as ISO 100 and f/40 useless. (There is a short description of these terms on page 72, but hardly enough for the novice and not early enough in the book to make the initial discussions helpful.) However, for someone who is truly serious about taking better photographs, this book provides a lot of informationmore than most people will be able to absorb in a single reading. I personally plan to read through some sections multiple times and use the book as a reference in the future. Whether this book makes me a better photographer remains to be seen. (As Harold says on page 46, “Cameras don’t take pictures; people do.”) I wish that there was more about the mechanics of performing these amazing tasks and better descriptions of the equipment the author used, but that may be asking too much out of a single book on a complex topic. Overall, I think the author has achieved his goals admirably and that anyone reading this book will truly be dazzled by what is possible.

Review of Breath & Other Ventures

I wasn’t quite sure how to categorize Breath & Other Ventures (written by William Bridges, Green Market Press), but for me it was a self-help sort of a book, so I classified it that way. You may very well classify it some other way, which is certainly your right. In reality, this book is both more and less than a self-help book. It won’t help you control your weight or manage your anger, but it does ask an intriguing and thought provoking question, “How do you want to live your life?” It’s a deceptively simple question of the same sort as, “Who are you?” Most people have no idea of who they are, much less how they want to live their life, so this is a helpful book indeed. (Don’t make the mistake of confusing this question with, “What do you want to do with your life?”, which is actually quite easy to answer in comparison.)

The majority of the book is a series of non-fiction short storiesthe author uses the term essays. It’s in three parts. The first part is literally about breathing. Although William includes a number of medical terms and diversions in the book, the focus is on the actual act of breathingsomething I’ll never look at the same again. You’ll find breathing in all its forms, including the breathing that takes place during various sorts of meditation. I’m not a Zen practitioner, but I do meditate daily to manage stress and make some sense of the chaos that’s my life. Such meditation is Biblicalit’s mentioned more than a few times even though I know most Christians sadly leave meditation out of their lives. By the time you’ve finished this first section, I assure you that you’ll no longer take breathing for granted either.

The second part is my favorite. It’s a series of short historical stories. I found them compelling. In fact, I started reading this section and didn’t put the book down again until I had finished it. The historical section isn’t about major events or places that most people would consider all that exciting. You’ll discover something about average people in Indiana. The stories are all about the author’s relatives in some way, but not necessarily exclusively about his family. He digresses into other areas, which makes for an interesting read. (There is even a ghost story included in the set of stories.) You go down the road and aren’t quite sure what to expect nextthe twists and turns keep the eventual goal hidden and elusive.

The essays in the third part of the book are more focused on how the author has lived his life. I probably could have done without the first essay on Obama, but then again, I’m not a political person in the sense that I would go out and protest something, knock on doors, or even make a contribution. On the other hand, I feel quite good about exploring every detail of a politician’s career before voting and will write a letter or two to express my dissatisfaction. For whatever reason, this particular essay didn’t speak to meperhaps it’ll speak to you. I did enjoy the essay entitled, “Ten Weeks with the Circus” quite a lot (it isn’t actually about the circusI’ll leave the details of it for you to discover).

The book also has a very short fourth part (19 scant pages) that contains a fictional detective story about GeeGee Dapple. I found the story quite entertaining and a fitting end to the book.  There is little doubt in my mind that GeeGee is the author’s alter-ego. It appears that there is a number of these stories and I hope the author eventually puts them together into a compilation. For now, this is the first GeeGee story I’ve read. The addition reminds me of the “final page” entries often found in magazines. It was a nice ending to the book that doesn’t necessarily fit in with the rest of the book but is merely meant to entertaina kind of finishing touch not found in many books today.

If you’ve ever read and enjoyed Garrison Keillor, you’ll enjoy William’s style too. It has that same free flowing musing that Keillor employs in his books. This book isn’t meant to be funny though, so there are some distinct differences in the way the two authors approach things. This author also includes more than few pieces of poetry, most of which I found a good read and thought provoking. The poetry isn’t just stuck in place either (like many books out there), it always has a purpose for being placed precisely where the author has placed it in the book. I found the author’s word choices interesting as well. For example, you’ll find “blissninny” on page 44 (I’ll also leave it to you to discover the meaning of this word). If you want to see some examples of the author’s writing, check out his blog.

So, does this book answer the question, “How do you want to live your life?” Of course it doesn’t! That’s for you to decide. The author is relating a story of how he has decided to live his life and I think the hope is that you’ll spend a few moments pondering your life as well. I certainly found myself pondering mine. If nothing else, this is the sort of book you want to read as part of your own personal voyage of discovery.

 

Dune

Dune is an amazing read that’s hard to strictly categorize. Most people say that it’s a science fiction book, which I guess it is to a certain extent. After all, it does take place in the future when mankind has moved out into the solar system and colonized many worlds. The book takes place so far into the future that all knowledge of man’s origins has faded into obscurity. There are certain technology elements to the book, but you won’t find robots, space battles, or anything of that sort. In fact, the author deliberately downplays technology and offers technology run amok as a reason for man’s venture into an almost anti-technology society.

In some respects, Dune is a fantasy. You’ll find mention of the strange spice melange which imparts almost magical characteristics to those who indulge in it (and almost everyone in the book does to some extent with differing effects). The backdrop for the book reads somewhat like a Gothic novel with kings and queens. The main character is a duke seeking to repair an incredible wrong done against his family. The book is also filled with the mythical creature, a sand worm that’s so large that people can ride it. Dune is a desert planet and it invokes a somewhat romantic view of the difficulty of living in such an environment.

However, in its innermost being, Dune is a book about political intrigue and the author, Frank Herbert, does an amazing job of creating a twisted plot. Because this book is a bit complex, some people will find it hard to read. Still, once you get into the meat of the book, you’ll find that it keeps your interest. Dune is for someone who likes almost Machiavellian complexity and doesn’t particularly relish a book with little substancemere mind candy.

The book has a strong cult following and you’ll find many follow on editions for it. In fact, two movies have come out about Dune in the past. The first is a shorter version (a little over 2 hours for the original theatrical offering) that stars Kyle MacLachlan, Virginia Madsen, Francesca Annis, Leonardo Cimino, and Brad Dourif. This version also includes Patrick Stewart before he became famous as the captain of the Enterprise in Star Trek. The second is a longer 265 minute version that stars William Hurt, Alec Newman, Giancarlo Giannini, Uwe Ochsenknecht, and Saskia Reeves.

Both theatrical versions of Dune diverge from the original book plot in a significant waythe book doesn’t spend much time discussing the action in battles, while the movies seem to focus on it to an extent. In fact, Frank Herbert is apt to simply say that the battle occurred and that a certain party won. Consequently, the movies and the book both have something to offer and are different presentations of the same plot. I enjoy all three and plan to review the movies at some point.

Dune is the sort of book to get if you want to become totally immersed and forget your cares for a while. The writing is good and you won’t find yourself distracted by inelegant prose. When you’re done, you’ll definitely find yourself wishing for more (and fortunately, there is more to be had in tomes such as Children of Dune).

 

Rod Stephens’ Visual Basic Programming 24-Hour Trainer

Learning a new skill, such as programminglearning it quickly and easily, is much harder than it sounds, but “Rod Stephens’ Visual Basic 24-Hour Trainer” makes the task considerably easier. The book begins with possibly the best Introduction I’ve ever seen. The author tells you precisely how to use his book to learn how to code in Visual Basic in a short interval. Additionally, he makes it clear what the book won’t tell you. This is most definitely a book for the rank beginnersomeone who has never written code before and the author makes it clear that better educated developers need not apply. (More advanced readers will benefit more from another of Rod’s books, “Visual Basic 2010 Programmer’s Reference“.)

The chapters tell you how to perform most basic tasks associated with desktop applications. You won’t find any Web development techniques in this book, but the author makes that clear in the Introduction. The reason for focusing on the desktop is that it provides a controlled environment that works anywhereno Internet connection required, no special setup needed. All you need is your system and Visual Basic.

The first chapter is the usual description of how to get Visual Basic installed on your system. Rod discusses a few different options and doesn’t wimp out by covering only Visual Basic 2010 Express Edition like many beginner books do. Because of the target audience for this book, Visual Basic 2010 Express Edition works fine.

The book takes the usual college approach of starting with a basic application, working through variables and structures, and then moving toward more complex application types. You learn all of the basics of working with classes, printing documents, working with the clipboard, and other usual fare for a book of this type. Rod does provide a couple of nice perks such as working with LINQ and databases using the entity framework. The goal is to learn how to use Visual Basic at a basic level, so these exercises will serve the reader well. Someone looking to start by creating a relatively complex example almost immediately will be disappointed. I know that some readers look for this approach now and Rod’s book definitely won’t serve their needs; this book is more traditional (and proven) in its approach.

Each of the chapters provides several methods to learn the material. You can read about the technique, try it yourself on your machine, work through exercises, and even watch a video. Most readers will find a technique that works well for them. Rod suggests using some or ideally all of the techniques to obtain a better learning experience.

The videos are a nice touch and Rod does them well. The longest video I watched came in at 17 minutes, the shortest at 4 minutes. He has a nice speaking voice and an easy manner of approaching the topic. The reader should definitely feel at ease during the presentation. Rod doesn’t resort to humor to cover up a lack of depth in his book. It’s not that he’s incredibly serioushe’s simply straightforward and businesslike in his approach.

Will you actually get through this book in 24 hours as the title says? I doubt it. I tried out a number of the chapters and found that I averaged about an hour in doing them fully (including the exercises) at a rapid pace. There are 39 chapters in the book for a total of 39 hours of training as a minimum. Even if you attack the book at a rabbit-like pace and skip some of the features, you still won’t get through it in 24 hours and manage to gain anything worthwhile. I’d suggest setting aside at least 40 hours of focused time to get through this tome.

The bottom line is that this is a great book for the rank novice to learn a new skill and discover the joys of programming. It’s not the sort of book that anyone who has written code before will want and it’s also not the sort of book that the impatient reader will find helpful. Rod has done a marvelous job of presenting a complex topic in a manner that will help most people get up to speed working with Visual Basic in a short time.