Customer Reviews

Access Database Design and Programming (Nutshell Handbooks)

5 star:		(22)
4 star:		(17)
3 star:		(1)
2 star:		(3)
1 star:		(3)

 

 

In Access Database Design & Programming, the author uses very mathematical and academic language. The database design part of the book is focused on the mathematical theory of relational databases. The programming part of the book is a reference work to programming with VBA.

All parts of the relational database in Access will be mathematically defined and proven. It will have a name you most probably will find confusing, and far from what you are used to from the Access interface. Apparently the author follows the naming standards established in the academic world to prove the algebra. After all, he is a professor of Mathematics !

In the programming part of the book you will be introduced to the DDL, DML and DCL components included in Access. Also, these components will probably be completely unknown to you, if you have no previous programming experience. Further, the book makes use of DAO as opposed to ADO.

The book is perfect for someone, who has completed courses in Computer Science, Programming and Algebra, or with the equivalent knowledge and a mathematical/academic way of thinking. They will be able to read through the book in a fast pace, and immediately make use of Access at a high level.

If your background is different, I would recommend another approach to database design and programming. For database design, I recommend "Inside Relational Databases" by Whitehorn and Marklyn (ISBN 354076092X). To learn programming I recommend "Learn to Program with VB 6" by John Smiley (ISBN1902745000).

This book is going to split its readers in two groups: The mathematically and academic minded who will love the book for its concise language. And the "grass roots" among the Access users/developers, who will be looking for database samples or VBA code snippets to learn from, and find none.

You will probably ask yourself if you need to know this much theory and detail. But remember, a relational database operates purely on mathematics. It is difficult and tiresome to learn, but your reward will be well worth the effort.

So you're familiar with the Access interface and are comfortable with tables, forms, reports and macros. So what's next?

Simply put, choose this book if you have little to no programming experience and you're ready to go to the next level with Access database development. This book is truly for the advanced Access user, but the novice VBA programmer. Having spent many frustrating hours with other books that claim to be for this audience, I can wholeheartedly recommend this one. I needed a "primer" in VBA before moving on to more advanced treatments, and this one fit the bill.

For me, a bonus was the section on normalization. Well written and clear, it solidified and enhanced my understanding of sound database design .

Steven Roman...thanks so very much!

This book provides good overview of the database design in the first four chapters. Good tips to avoid data redundancy without losing data. Chapter 5 and 6 throws light on SQL, DDL and DML components of Access SQL, not too much but some how enough. Chapter 7 gives a little bit idea about the Database Architecture.

Then Chapters 8-13 provide basic introductory and definitive approach of VBA in Access with different data types, functions, sub-routines, control statements, etc.

Chapter 14-16, here goes the real thing about DAO. With couple of examples, author explained in very good manner about different aspects of Data Access Objects and how to open, create and query database/tables from within code.

Chapter 17, explains breifly about ActiveX Data Objects incl. ADO and OLE DB.

So over all, this book is very good and to the point. I would definitely recommend to the beginners who wanna learn MS ACCESS or who has a little bit knowledge and wanna improve it without wasting time and going through huge books. As far as, MS Access professionals are concerned, they may not find it very informative but still if they go direct through chapters 14-17, they may find something useful.

I have yet to go wrong buying an O'Reilly book. This book is no exception. Few screen shots clutter up the book, which is great. It seems that most other Access books jam a bunch of screen shots in the book just to make the book thicker and therefore command the greatest bookshelf real estate. Do I really need screen shots showing me how to use a wizard? Isn't the wizard supposed to walk you through the steps so that you don't need a book? This book doesn't insult you like so many others. I bought the second edition. It was excellent at explaining database theory. Considering that Microsoft will eventually phase out DOA and move to ADO, I was a little bit disappointed to find heavy coverage of the former and light coverage of the latter. However, once you understand the theory behind DAO, the light coverage of ADO is all that is needed to explain the differences.

Excellent book.

I first read Steven Roman's book on Access a few years ago when it was written for Access 97. I recently bought a copy of the current version as a reference.

What I liked about Steven's books was that he took seriously his coverage of normalization, which is rare amongst books on Access. If you're new to database programming, you need to learn the basics of normalization. In my experiences, I've come across a lot of databases designed by beginners that exhibit a "spreadsheet" type of understanding towards Access tables. The beauty of the relational model is that once you have your database set up, ongoing maintenance is minimal. If you learn how to program Access, but don't learn the basics of normalization and the relational model, you may as well just keep your data in Excel spreadsheets.

My complaint with this book is his coverage of ADO. The author clearly prefers DAO for MS Access, and he states as much, and his coverage suffers. He covers the material, but he makes using ADO appear to be very difficult. In an entire chapter on ADO, he fails to show the user the most basic thing: how to generate a recordset for a table in your Access database. Instead, he shows you how to use ADO to query other databases, such as SQL Server and even Excel, but not the Access Database that you're currently using.

In DAO one of the fundamental details that you need to know about is the CurrentDB object. Steven gets a gold star, because he not only covers the CurrentDB object, but he spends 6 pages on it. In ADO, an object that is used for a somewhat similar purpose is the CurrentProject object. You won't find coverage on it anywhere in this book - just check the index. Perhaps the author's surreptitious goal of the chapter is to frustrate you so much with ADO that you will return to DAO, his preferred choice. Tsk, tsk Steven.

After reading the books section on ADO over and over again, I cannot recommend this book if you plan on owning only one Access book. Instead, I would recommend Alison Balter's Mastering Access Databases. It is the best Access book on the market(as most Amazon reviewers will attest to) and covers nearly ever topic that you'd want to know about Access.

Even so, Steven's book covers normalization so much better than the other Access books out there that I would advise serious Access programmers to buy two books: Alison's and Steven's.

True to its title, this book has an excellent section on database design, particularly as it pertains to Microsoft Access. However, I found it particularly frustrating when none of the code examples in the book worked with my databases. When I read Balter's "Mastering Microsoft Access 2000 Develoment", also available at Amazon, I found out why. DAO has been replaced by ADO. This book covers DAO first, and mentions only later. I spent five days trying to get DAO to work and failed. I am so glad I had my other Access book to steer me straight.

The great introduction to relational databases is useful, but you could glean the same information from Hernandez's "Database Design for Mere Mortals" and it would apply to all DBMSes.

I hate to give an O'Reilly book a bad review, but this one didn't meet my expectations. It is advertised to apply to Access versions 97-2002, but I don't think it is as up-to-date as some of the other books on the market.

Most 1,000 page books on Access show you a bunch of worthless screen shots and help you put together a rather useless "college" or "restaurant" database. The problem with these books? They never explain what a database is and why you might want to use one. Steven Roman is incredible at breaking the complex down to the understandable for the intelligent non-technical user. Forget dummies books, you are intelligent or you wouldn't be thinking about using Access! It is so much easier to use Access when you understand what a databse is. I can't give enough praise for this book.

An excellent introduction to sound database design theory and how to execute it with Access. It gives you enough nuts and bolts so you can figure out what is going on but not so much it bloats the book unnecessarily. An excellent choice for the new database designer or old Access hand looking to take their skills to the next level.

I have been using Access via the GUI interface for some time now, and I have had considerable experience with Basic and some experience with Visual Basic. What I wanted was a manual that clearly explained how VB is implemented in Access. What I DIDN'T want was yet another manual to tell me how to create tables, fields and queries in the GUI; drag and drop controls from the toolbox onto forms and reports; program events via the wizards; yadda yadda yadda in the first 10 chapters, then leap way ahead to programming complex events and procedures in Chapters 11 and on. I'm tired of books like this--they treat you like an idiot for the first 10 chapters, then they treat you like a programming genius for the rest of the book. What I needed was a more gradual transition between the Access GUI, and use of VBA in Access. A book that could create a "context" for VBA in Access. Steven Roman's book does just that--especially chapters 9 (Data Access Objects), 10 (Programming DAO - DDL), and 11 (Programming DAO - DML). Roman provides a couple of very useful and intutive charts to visually represent the DAO and Access Object hierarchy (I refer to these charts all the time), and Appendix A provides a convenient list of all the object classes, including their properties and methods (much more intuitive to me that that prickly object browser in Access). A TableDef object variable exists in the TableDefs collection? A QueryDef object variable exists in the QueryDefs collection? Duh. Why didn't any previous reference books make this clear to me? I've still got a way to go before I'll ever be a skilled developer in Access, but at least now I have a more contextual and systematic understanding of the object model (rather than a bunch of disorganized and poorly integrated VBA constructs). I would recommend this book to anyone who can create tables, queries, reports, and design forms in their sleep, but who are unable to do much else (without wizards) because VBA just doesn't make sense to them. (I have had no formal training in programming, everything I know about programming I've learned on my own--thus I think I represent a unique target audience that most computer programming books miss.) This book helped me "make some sense" out of VBA in Access, and now I think I can move forward.

Most books on Access are over a thousand pages long, and teach you bad habits like designing your database to fit your forms, not vice-versa. This book, like other titles from the publisher, is information-packed and concise. Unlike other Access books, this title teaches you to resist the urge to bind (pun intended) your tables too tightly with your forms. Instead, in a very easy-to-understand way, it teaches you to design your database well first, and then take advantage of the programming tools that are part of Access to manipulate your data. Other books emphasize form design over all else, teaching an approach that invariably paints the budding database designer into a corner sooner or later. The reader who uses the approach taught in this book will design extensible databases that look a lot like the ones the n-tier SQL Server and Oracle gurus put together. I've helped colleagues with databases, and then urged them to get a copy of this book for themselves -- You know, "Give a man a fish, ..." Learn to design Access databases the RIGHT way and avoid wasting your time plowing through yet another cinder block-sized tome - buy this book.