Expert One-on-One Microsoft Access Application Development

Expert One-on-One Microsoft Access Application Development
Authors
Helen Feddema
ISBN
0764559044
Published
07 May 2004
Purchase online
amazon.com

If you are developing databases for your own use, the process need not be complicated. But when you build databases for clients, many of whom may not be familiar with Access or comfortable with databases in general, you have a lot more work to do. Expert One-on-One Microsoft Access Application Development makes that process easier. In these pages, you discover how to set up tables and relationships to ensure that the database is properly normalized.

Page 2 of 2
  1. Editorial Reviews
  2. Customer Reviews

Customer Reviews

K. Ambrose said
Like all programming books, the trick is to match the reader's current level and skill set with the level of information presented in the book. On a scale of 1 to 5, the vba programming training here is about level 2 in my opinion. This is not bad training, it is just not at an advanced level. You should probably have some previous knowledge of vba but if you are an experienced vba programmer the only areas of interest are likely to be the word/excel integration issues.

T. L Waltz said
I bought this book hoping, as the author stated in her introduction, to make the transition from an experienced and competent Access user to an Access developer who can make a living developing applications for clients. I had hoped that the book would be chocked full of tips, tricks and wisdom from an Access expert. But I was disappointed. The author stated that she wrote this book for experienced Access users, who knew how to create tables, queries, forms and other Access objects, and had some familiarity writing VBA code. It has always been my opinion that the creation of a good Access database application requires a solid knowledge of VBA, the available control events and how to effectively program those control events. Unfortunately the chapter on VBA was rather weak and the chapter on controls had little discussion of the numerous control events.

On the other hand, the author presented 13 full pages of VBA code to demonstrate using the ItemsSelected collection of a MultiSelect listbox, a concept that could have been demonstrated in about 10 lines of code. I found it interesting that the author never mentioned the Control Wizard, which can automatically generate VBA code for many control events. Also the author never mentioned that a callback function could be used as the record source for a combobox (or listbox).

In the first half of the book the author uses the Toy Workshop database example to illustrate how to create/modify tables, relationships, forms, controls and reports. The reader very quickly must become familiar with the structure of this database. A complete summary of the tables (listing the fields), forms (listing the controls), queries, and reports in an appendix would have been very helpful. The reader is almost forced to download the sample databases from the Wrox website to get anything out of the book.

The author had many pages presenting the three add-ins that she developed: Design Schemes, LNC Rename and the Menu Manager add-in. On the surface these add-ins appear to be good tools for an Access developer, but the LNC Rename add-in (used to rename objects using the Leszynski naming convention) was not designed to work for controls with existing VBA code. And I wasn't crazy about the design of the main form created by the Menu Manager. Not to mention the fact that this add-in required you to rename your main form using a non-standard "fpri" tag. I would have liked for the author to give me the expert guidance that I need to create my own add-ins rather than to simply use the "canned" add-ins developed by the author.

I didn't read the chapters on Automation dealing with Word, Outlook or applications outside of Office. The chapter "Working With Word" probably is one of the best chapters since this subject appears to one of the author's areas of expertise. I did read the chapter on "Working with Excel". It was OK. It just scratched the surface of the subject of automation between Access and Excel, primarily dealing with how to programmatically export data from Access to Excel and import data from Excel into Access.

Before you decide to purchase this book, I'd recommend taking a look at Alison Balter's book "Mastering Microsoft Access 2000 Development " and Scott Barker's book "Microsoft Access 2000 Power Programming". And if you decide to purchase this book, plan on downloading the sample databases (Note: the three ZIP files are a whopping 114MB) and plan on spending a lot of time studying the sample tables, forms, queries, reports, and VBA code.

Allan Bach said
Helen has been around since Access was introduced. She knows how to solve problems. This book is better than her previous book (Microsoft Press) for Access 2002. Great examples, plenty of code. Helen gives the reader insight into every day solutions. I especially like her Menu Manager Add-in. It is a good help for using her solutions. And, she even has code for sending a fax from Access with WinFax. I wrote my own procedure (it took a great deal of time) and it works fine, but Helen's code is very efficient (over 20 pages devoted to this in her book). It checks for all the folders and sends the fax. Much more information included - from a sample interview with a client, to using Access with Word, Outlook, and Excel.

My only complaint concerns the sample files. Wrox used to include a CD, but now they seem to be leaining toward web downloads. Not a bad idea but, in this case, the files are over 100 MB. If you don't have broadband, you may be working in Access 2004 before you're finished downloading these samples.

You might also like...

Comments

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Beware of bugs in the above code; I have only proved it correct, not tried it.” - Donald Knuth