Customer Reviews

Access 2003 VBA Programmer's Reference (Programmer to Programmer)

5 star:		(7)
4 star:		(1)
3 star:		(2)
2 star:		(1)
1 star:		(2)

 

 

I am writing this review because I believe the expectations created by the book description and reviews were not met.

I do not disagree that the book is comprehensive as the description and the reviews point out. It discusses subjects that are wide-ranging and, I am certain, very important to many readers.

My contention is that the book is not organized in such a manner as to allow a less experienced user to get at what he wants. I think books like these need to better indicate for whom they are written. The foreward talks about it being for those who have been using Access for some time and are just beginning to jump into the world of code. I have had a reasonable amount of experience with Access, relational databases and electronic spreadsheets. I have a decent understanding of programming although only little expereince with object oriented programming.I feel that I understand Access sufficiently well that I have a base upon which to add the VBA skills. I really don't believe that the book is written for such a person.

My opinion of the shortcomings follow.

I believe the most important component of a reference source is the index. In this case the index is 24 pages with 100 entries on each. The frustration I faced in trying to answer my questions through the index, and table of contents was as bad or worse than trying to use Microsoft help screens or on-line resources.

I do not understand the organization of the book. It does not seem to follow a path from broad to narrow or any other progression that makes intuitive sense. I know this is acceptable in a reference but only, I would say, if there was a sufficient index.

The general execution of the book was also inferior. I was frequently distracted by grammar errors such as the wrong word (eg "than" instead of "that") and even typos. The figures and tables were numbered but not titled and in at least one case was misreferenced from the text. I found myself really in need of a diagram in many cases but there were none to be found. The car analogy used to explain Object Oriented Programming was not clear and I think possibley incorrect. The analogy describes "Press" as a method of the "Gas Pedal" object when it seems to me to be more like an event triggered by the user. I am not saying that I am necessarily right or the authors definitely wrong. I'm just saying that the analogy was ineffective. Again, I would have loved (and expected) a diagram or some representation that would explain this difficult concept.

I want to say that in the end I did find the elusive answer to my question although just by chance. I think this will illustrate my frustration with this book. I wanted to know how to automate the import of a TXT file. I had searched on-line help and 2 other Access books as well as this book but could not find the answer. I finally was skimming through the methods of the DoCmd Object in Appendix E (The Access Object Model) and happened on the DoMenuItem method (page 750.) The description of this method explained that it executes the specified menu item but that it was a legacy from Access 97 that had been replaced by the RunCommand method in later version of Access. I then flipped forward in the same appendix to the RunCommand Method Arguments section (page 793) which started with this comment: "One of the easiest ways to perform a variety of functions in Microsoft Access is through use of the RunCommand Method." I thought that if it was so easy, then why doesn't somebody include it in their discussion of VBA. (I don't know if this book does so because the only reference to the RunCommand in the index is to the Appendix pages noted above. There are no references to the DoCmd or menus in the index.)

When I found this discussion, I knew that I had answered my question but I still had more errors to deal with. The section was entitled RunCommand Method Arguments but the verbage that preceded the table stated "The RunCommnad takes a single argument, the acCommand constant. All of the available acCommand constants are listed in the following table." The column in the table that follows is entitled "Argument." I know that constants can be arguments but don't these constants relate to the acCommand which is the only argument of the RunCommand? I know this is picky (and I feel more than a little self-conscious for exposing my ignorance) but doesn't a book about language need to be precise and consistent in their use of terms?

I would also ask what the value is of this (the RunCommand Methods Arguments) table. It simply lists the constants (Arguments [?]) This information is available and more easily accessible in on-line help. The inclusion of this table (and possibley others) may make the reference more complete but does not necessarily make it more valuable. At the risk of beating a dead horse, I feel this table illustrates another shortcoming of this text in that it isn't even organized very well. The 9 page table has two columns that list the constants alphabetically. The first column starts on page 793 with acCmdAboutMicrosoft and finishes on page 802 with AcCmdPivotChartDrillInto. The list continues in column 2 back on page 793. I know this is confusing but so is the book.

I have no doubt that the authors of this book are extremely knowledgeable (and even really good and helpful people.) I would love to know what they know. That is why I bought this book. I can't imagine the difficulty in trying to organize and explain such a large and complex model but that is what they have attempted to do. I would love to see this book reworked and represented in a better way because I think think it contains a lot of good information. I just don't think enough consideration was given the user or enough care was taken in the execution.

This is a very special book. The authors obviously went way out of their way to include everything that you could need to be a successful Access developer. As far as I know, this extensive reference material has never before been assembled in one place. As a result, it is just the right thing for aspiring intermediate and advanced users of Microsoft Access. Even many developers with extensive experience will be surprised at what can finally become clear to them by checking out what this reference makes available. You'd have to search the Microsoft and other sites for weeks to assemble all this on your own.

This well-written reference covers everything from VBA basics to using the new Access Developer Extensions, which are part of Visual Studio Tools for the Microsoft Office System. In between it also covers error handling, enhancing forms, enhancing reports, SQL coding, and even working with the Windows Registry. The appendices go all the way from A to L, or from Upgrading of Access (what other book covers this subject at all, never mind so thoroughly?) to VBA Reserved Words.

I have never seen such comprehensive reference material! And is it loaded with tips, tips, tips! The authors have obviously lived in the trenches with Access for some time. They know what to watch out for. They know what kind of protocols you should set up yourself to boost your success.

It took the experience of four co-authors and several other contributors to bring this work together. Patricia, Teresa, Graham and Armen have provided a unique Access reference that will get you up and going fast and save you scads of time that you would otherwise have wasted learning "the hard way" or, at best, wasted digging through a multitude of written and online references. This is a special, one-of-a kind reference work!

I own this book along with Wordware's Access 2003 Programming by Example with VBA, XML and ASP. I find that this book has a more comprehensive treatement of subjects such as using ADE, Access upsizing via ADP versus MDB databases with linked tables and DAO. Granted that DAO is quite dated but its inclusion in the book is prefaced by a discussion of the advantages that it has over ADO in some limited applications. The book also tries to provide a balanced view of the advantages and disadvantages of each technology, even if it does spend more of its time concentrating on DAO.

If you are looking for a serious reference on ADO, I would suggest that you give the Wordware title serious consideration. However, if you are comparing ADP versus MDB databases in upsizing scenarios or if you are looking for a good reference on ADE which is well rounded in its description of VBA as applied to Access in general; as opposed to a specific data access model such as ADO, then this is the book for you.

The writers have done this all before and approach the subject in a narrative tone which worked for me. The section on ADP sold me on the book as I was looking at an application for upsizing an Access database to SQL server, whilst still retaining Access for the forms and reports. I was considering the two main approaches of using ADP versus MDB with linked tables and this book was able to provide me with all of the information required for me to make a sound decision.

In fact I liked it so much whilst browsing it at my local Boffins bookshop that I just had to buy it on the spot! However, whilst very good, it is not worthy of 5 stars due to its excessive focus on DAO.

As an Access Developer this is one of my most used Access VBA reference books. All of the authors present the material in a good comprehensive manner for all levels of Access development. There are many clearly presented code examples and Access information that will assist in all levels of development.
There are many good chapters in the book; however don't overlook the Appendices as they are exceptional.(Note: Appendix I "Tips and Tricks") I know most Access Developers are selective in the books they buy. If you scan this book you will see how much above other VBA reference books this particular book is.

Read the title before you buy this book. The book is a reference for Programmers already familiar with Access and it shows a lot of examples which can be used by most Programmers. If VBA Programming is new to you, you should start with a "Step by Step" book and then afterwards carry on with this book. Personally I missed the declaration of variables in this book (as well as in most other books about Programming).

I have to agree with reviewer Paul E. that the authors did an outstanding job on this book.

The book is comprehensive, covering just about everything you need to know when you're working with Access application development.

For me, the 250 pages or so of appendixes have been the most useful, but there's also a sixty-page chapter on database security in the middle of the book that should be required reading for all Access developers.

Here's the table of contents from my copy of the book:

Introduction.

1. Intro to Access.

2. Access, VBA, and Macros.

3. New Features in 2003 (and 2002).

4. VBA Basics.

5. Using the VBA Editor.

6. Using DAO to Access Data.

7. Using ADO to Access Data.

8. Executing VBA.

9. VBA Error Handling.

10. Using VBA to Enhance Forms.

11. Enhancing Reports with VBA.

12. Creating Classes.

13. APIs.

14. SQL & VBA.

15. Working with Office Applications.

16. Security.

17. Understanding Client-Server Development with VBA.

18. Windows Registry.

19. Using the ADE Tools.

20. Macro Security.

Appendix A: Upgrading to Access 2003.

Appendix B: References for Projects.

Appendix C: DAO Object Method and Property Descriptions.

Appendix D: ADO Object Model Reference.

Appendix E: Access Object Model.

Appendix F: Windows API Reference Information .

Appendix G: Naming Conventions.

Appendix H: VBA Reserved Words.

Appendix I: Tips and Tricks.

Appendix J: ADO Object Argument Information.

Appendix K: Access Wizards, Builders and Managers.

Appendix L: Windows Registry Information.

I am a Microsoft Access MVP (Most Valuable Professional) and I learned how to write VBA from this book. I cut my VBA teeth so to speak with it. My book is now dog-eared and scribbled all over with many notes. Studying it cleared my understanding of Recordsets, Objects, Properties, Methods, Events, Arrays, Loops, Classes, and more. It helped me to learn to write quality code which has saved me a lot of time. I continue to use this book as a reference. This is one book where I use the Appendex almost as much as the Chapters. The Access, DAO, and ADO Object Models are very helpful. The Appendex also includes naming convention which can save a lot of time when writing code and will make your code more easily understood by others. A list of Reserved Words and Special Characters are also included so you can avoid the errors caused by using them in the wrong places. This book was invaluable in helping me to write VBA.

I started working with VB back at the turn of the Century (yes, that was 8 years ago), same with ADO and databases in General. A little of this here, a little of that there It wasnt till the last year that I had to do VBA and Access, and this book brought it all together.

Its not for a beginner. They dont discuss writting queries, or designing data bases nor branching and decision making. It DOES talk about Macros, Objects, Security, API and how to use the tools in Access to make full featured Access application and integrete it with other MS Office products. It gives subtle nauances that you just cant find no matter how often you push F1

I was getting this stuff on my own of course, but trying to figure out something from the Help documentation and NorthWind just wasnt doing it. Our clients give my consulting company a lot of money to get things done This book was just what I needed consoldate my skill set and meet our clients needs.

I have built some pretty significant excel forms & processes using the VBA environment. This book does little to take you into developing in ACCESS. The examples are poor, inconsistent and too vague for a newbie to the environment.

I count 6 MS Access books on my shelf at work. If I could only have one, it would be this one. I find information that I haven't found in any of the others. It's also the best reference on Access SQL. I'm in the process of developing from a casual access user to professional level, and have lots of questions.