Creating databases and unexpected error messages go hand in hand. Access (97 or 2000) isnt exactly a walk in the park, and while most error messages have a help button, it doesnt go far enough to fix the problem, leaving users with that fun task of slowly trying to figure out where they went wrong.
Creating databases and unexpected error messages go hand in hand. Access (97 or 2000) isnt exactly a walk in the park, and while most error messages have a help button, it doesnt go far enough to fix the problem, leaving users with that fun task of slowly trying to figure out where they went wrong.
Troubleshooting Microsoft Access Databases shortcuts this with a flowchart approach to problem solving, and if that doesnt work, the members only section of the Microsoft-backed Web site opens many more solutions.
Written for the beginner and intermediate in mind, the book is easy to read - in seconds you can find a solution to a particular problem. The chapters are logically titled, and organised alphabetically. The first part of each chapter is a flowchart. It might have been easier if all of these where put together at the front of the book, as flipping from chart to chart is awkward. The flowcharts start with a broad question and drill you down til you find the solution. If it is a quick fix, the solution is there on the flowchart, while if it is more complicated, the solution page number is given. If the problem isnt on the flowchart at all, each chart has a list of related chapters. Theres an extensive index, and a Web site for further resources.
The problems are generally those beginners and low level intermediates would come across - for example there is virtually nothing on modules, but there are solutions to macros, queries and so on. The solutions start with the source of the problem, normally a paragraph why the problem occurred to help you ensure it doesnt occur again - a great idea.
This Review appeared in the August, 2001 issue of PC & Tech Authority Magazine
