It is clear from the positive reviews that this book is a success for an audience of advanced VB programmers. Those of us that are less advanced (I'm a beginner) might ask whether we are going to have the "two-star" or the "five-star" review experience. How much VB do we need?
An example I ran into might help you decide. On p. 178 the author describes an example of an "array of arrays" creating an appointment calendar with descriptions of appointments stored in the array of arrays named "apps(day)". As part of the code, the satement appears
If IsEmpty(apps(day)) Then
I was surprised to find that IsEmpty ALWAYS evaluated FALSE, making this If statement useless. Once this problem was discovered, I found from the online help that IsEmpty always evaluates false unless apps(day) is a simple variant. (Do you know this? I had to find out.)
Can apps(day) be a simple empty variant? It's supposed to be an array of arrays. Well, if you initiate apps(day) with
apps(day) = Empty
then the If statement works. But if you initiate apps(day) with
apps(day) = Array(Empty)
which is how it's done when apps(day) is NOT empty, for example,
apps(day) = Array("First meeting of day", "Second meeting of day")
then the If statement won't work unless it is changed to
If IsEmpty(apps(day)(0)) Then
(What do you know about arrays, array notation, how empty array notation changes when it fills? I had to find out.)
What does this have to do with evaluating the book? The above example is not unusual. If you are happy to read at an abstract level, the gist of the examples is clear, and the examples are interesting. In the above example, it's clear what the IsEmpty is about, and the "array of arrays" idea is great. However, if you want to implement the author's ideas using his code, his elliptical approach leaves gaps and ambiguities. Depending on your VB background, the needed fill-in and clarification can require much head-scratching.
Bottom line: As a stimulus to the imagination, definitely go ahead. As practical coding, be prepared to fuss.