Comparison to the Built-In Microsoft Access Database Documenter

Why bother getting Total Access Analyzer when Microsoft Access includes a built-in database documenter?

If you think the database documenter is all you need, think again! This comparison shows how Total Access Analyzer gives you the information you need to build better, more robust Access databases. Winner of every Best Access Add-in Award, Total Access Analyzer let's you take control of your databases.

The built-in Access database documenter is a basic tool that creates a limited set of documentation, but does not include the features you need to really understand what's happening in your database. It documents each object independently and does not consider the database as a whole.

Total Access Analyzer takes a different approach. It documents your entire database to reveal the hidden relationships among your database objects. That's the only way you can determine broken references, where objects are used, which objects are unused, etc. The extensive reports, error detection, suggestions, and other output makes it a must have for any serious Access user or developer!

Feature	Total Access Analyzer	Built-In Access Database Documenter
Top Reasons!
Database Overview	Examine your entire database to get an immediate overview of what's in it (example)
Object Cross Reference	Examine your entire database to find how objects relate to each other
Module Code Analysis	Comprehensive VBA code analysis including procedure and variable cross-reference with recommendations (summary)
Macro Documentation and Analysis	Macro command syntax checking and formatted printouts. Find all embedded macros in one list.	Macro printouts are a mess
Error Detection	108 types of errors that may cause your database to crash (list)	0
Improvement Suggestions	146 ways to improve your database such as finding unused objects and code (list)	0
Performance Suggestions	46 ways to improve performance  (list)	0
Useful Reports	390+ presentation quality reports with customizable headers and colors. Many reports also support filtering.	Only one non-customizable report per object type
Searchable Documentation	Our powerful treeview form makes it easy to examine the results. Search feature finds any string across your properties and code	Output in report preview only without search capability
Save Documentation for Multiple Databases or Versions	Documentation is automatically saved so you can refer to previously generated documentation	Automatically deleted each time
Errors and Suggestions Highlights
Find references to objects, fields, or code that don't exist (renamed or deleted)
Find corrupt objects
Verify function references and parameters from forms, reports, and macros
Detect Unused Objects	Tables, queries, forms, reports, macros, classes, procedures, TempVars, variables, etc.
Verify data types of identically named fields are consistent
Detect duplicate SQL in queries and form/report record sources
Detect duplicate hotkeys on a form
Catch command buttons without code
Find procedures without error handling
Flag public procedures that should be private
Detect DAO and ADO data types variables not explicitly defined
Cross Reference Analysis
Tables used in queries, forms, reports, macros and module code	example
Fields used in tables, queries, forms and reports	example
Queries across forms, reports and modules	example
Macro calls across forms, reports and modules	example
Temporary variables (TempVars)	example
Module cross-references (classes, procedures, variables, labels, etc.)	Extensive (Summary of all Modules) (Individual Module Overview)
Functions called from forms, reports, queries, and other modules
Diagrams (Multi-level Cross-Reference)
Application flow (see how the application works as objects, events, and procedures call each other)	example
Data flow (how data flows from tables, through queries, forms, reports, and code)	example
Object references (other objects referenced by forms, reports, and queries)	example
Module Printing
Print module text (modules, forms, reports) with line numbers and procedure index	example
Print module code with loops and logic indented and bracketed	example
Specify line continuation character to easily see line breaks	details
Select fonts for code vs. comments
Line shading ("green bar") option
Module Analysis
Procedure definitions	example
Procedure calls (parent to child) cross reference	example
Procedure usage (child to parent) cross reference	example
Unused procedure detection
Variable cross reference
Unused variable detection
Modules without Option Explicit set
Procedures without error trapping code
Declarations to DLL procedures
Label cross reference
Cleanup (stop and debug) cross reference
User-defined type references
Enumerated type references
WithEvents usage
Class module usage
Visual Documentation
Form image (blueprint)	example
Report image (blueprint)	example
Annotated controls to show hidden controls
Output Reports
Number of reports	390+ list	Only one per object type
Reports by Object Type	Many	One
Reports with Sort Options
Select multiple reports to print at one time
Filter reports by object name or type
Customize report headers and colors	details
Output available for future use		Always deleted
Export one more more reports to other formats	PDF, HTML, text, RTF, Snapshot, and XPS
Ease Of Use
Specify properties to document
View documentation with forms		Only print preview
Search documentation for values
On-line help
Printed user manual	Printed, extensive, and indexed: 188 pages
Basic Documentation
Object inventory
Summary of tables, field and record counts, etc.	example
Table and field definitions	example
Table fields, sorted by field name to see which tables use the same field names	example
Linked table attributes
Relationship linked table path
Referential integrity settings		Partial
Query tables and joins
Macro arguments as text		Partial, sometimes just numbers
Workgroup documentation of Users, Groups, Permissions, Options		Partial, Permissions only
ADP tables documented
ADP views documented
ADP stored procedures documented
Saved Import/Export specifications

Discover why so many Access users and developers insist on running Total Access Analyzer on their databases before they ship it to others! After all, why risk your reputation when Total Access Analyzer can catch problems before your users see them?

Additional Resources

Here's a paper we wrote that may help your situation:

Taking Over (Inheriting) Legacy Microsoft Access Database Applications