<< 1 >>
Rating: 
Summary: A must have for MsAccess programmers
Review: Daily employed subjects, very good explaineds and an useful INDEX to found what you need. That is aplicable to the whole serie "Access xxx Developer's Handbook". I own all of them!. The best book about MsAccess.
Rating:
Summary: A must have for MsAccess programmers
Review: Daily employed subjects, very good explaineds and an useful INDEX to found what you need. That is aplicable to the whole serie "Access xxx Developer's Handbook". I own all of them!. The best book about MsAccess.
Rating:
Summary: Rawk
Review: I bought it when it came out.Great book for Access97. Great chapters on string handling in the enclosed VBA book as well. Werd.
Rating:
Summary: A terrific handbook for every Access developer!
Review: I purchased these books, and within 10 hours, they had already profited me much more than the price of the books. I would recommend these books to anyone. They are worth their weight in gold.
Rating:
Summary: The Most Valuable Book I've bought all year!
Review: I purchased these books, and within 10 hours, they had already profited me much more than the price of the books. I would recommend these books to anyone. They are worth their weight in gold.
Rating:
Summary: The most important book for the advanced Access Developer
Review: I've bought every edition of the Developers Handbook since Access 2.0, and convinced every employer of mine during that period to buy a copy, too. I used to be amazed at how I could look for the solution to some Access problem in three other books and never find it (or even clues that helped!); then I'd look in Getz et al and find the *exact* solution, on a silver platter. In the past few years, I'll admit, I have on a very few occasions looked for something I didn't find. Once the answer was there, in quite thorough form, but I missed it because I looked in the index instead of the table of contents! The only reason I even mention this is that the Developers Handbook is the *only* technical book I've ever come across from which I have, almost subconsciously, begun to expect not just excellence, but PERFECTION! I realize how terribly unfair this is, but I can't help myself. I'm pleased to see the scope of the Developers Handbook being expanded into SQL Server and Visual Basic, since high-end Access development can no longer be done in isolation from those tools. Having a resource like this one provided by Ken Getz, Paul Litwin, and Mike Gilbert is far from the worst reason you could have for choosing Access, SQL Server, and VB over some other set of tools. If you're a developer and value your own time, you'll want this book. If you employ developers and you're lucky enough to have one or two who will actually *use* a book if it's available, buy this book now. The only way it won't pay for itself is if *nobody* ever opens it. And I'm not even sure of that. I think it might even make your developers better at what they do just by sitting on the shelf of their office!
Rating:
Summary: The most important book for the advanced Access Developer
Review: I've bought every edition of the Developers Handbook since Access 2.0, and convinced every employer of mine during that period to buy a copy, too. I used to be amazed at how I could look for the solution to some Access problem in three other books and never find it (or even clues that helped!); then I'd look in Getz et al and find the *exact* solution, on a silver platter. In the past few years, I'll admit, I have on a very few occasions looked for something I didn't find. Once the answer was there, in quite thorough form, but I missed it because I looked in the index instead of the table of contents! The only reason I even mention this is that the Developers Handbook is the *only* technical book I've ever come across from which I have, almost subconsciously, begun to expect not just excellence, but PERFECTION! I realize how terribly unfair this is, but I can't help myself. I'm pleased to see the scope of the Developers Handbook being expanded into SQL Server and Visual Basic, since high-end Access development can no longer be done in isolation from those tools. Having a resource like this one provided by Ken Getz, Paul Litwin, and Mike Gilbert is far from the worst reason you could have for choosing Access, SQL Server, and VB over some other set of tools. If you're a developer and value your own time, you'll want this book. If you employ developers and you're lucky enough to have one or two who will actually *use* a book if it's available, buy this book now. The only way it won't pay for itself is if *nobody* ever opens it. And I'm not even sure of that. I think it might even make your developers better at what they do just by sitting on the shelf of their office!
Rating:
Summary: A terrific handbook for every Access developer!
Review: These guys know their stuff. First of all the layout is a masterpiece. I don't know if the publisher should be thanked more then the authors. The font styles, size; page design is very pleasing and professional to say the least. The material is presented with a first person view. The "Event Model" is broken down so that you really know what happens when you create event driven functions. Coverage of VBA classes is a charm. An entire chapter for printer control is an award winner. I can't sing enough praises of the Access Developer Handbook. Pick up a copy and you'll see for yourself. Note: The book assumes you know some VB or VBA, and a light knowledge of the Access environment. P.S. I only wish that the authors would co-develop a book such as this on MS Visual Foxpro --We desperately need one!
Rating:
Summary: A must have for the serious developer
Review: These guys know what they are talking about. In depth coverage of many things not covered in intermediate books. If you are an Access developer, and/or VB, these books are an invaluable tool. You can tell from the beginning, that these are two of the best books, written by the best in their field. These will be the two most used reference tools I may ever use. Definitely worth the money, and more!
Rating:
Summary: Thanks, guys!
Review: You've saved me from another deadline late-nighter. A short summary is in order: 1. Combo-box auto-lookup wasn't working 2. Read on-line help 3. Read Microsoft's Building Applications 4. Read O'Brien/Pogge/White 5. Read Viescas 6. Read p.346-7 of Litwin/Getz/Gilbert: Tah-dah! The text is accurate and the examples work. I guess what made the difference is that the demo database was devoted to the specific subject that I was interested in, instead of having to wade through Orders or Northwind yet again. Is there a Pulitzer for computer books?
<< 1 >>
| 
