Analyzer, by FMS Inc.,
generates comprehensive documentation and
analysis of your Microsoft Access databases. It can analyze all
your objects in your database to generate how it all works.
cross-reference and detail information is gathered for tables,
fields, indexes, relationships, queries, forms, reports,
controls, macros, modules, users, groups, permissions, and more.
Print the relationship window and module code with bracketed
loop. Versions are available for Access 2003, 2002, 2000, and Access 97.
All output is stored
in an Access database. You can view and search the documentation
using the sophisticated multi-table forms, print the output using
any of the program's 225+ reports, or perform your own analysis.
This update also
introduces several new features and enhancements, including:
- Documentation is
- The "New Values"
field property for Autonumber fields ("Increment" or "Random")
- For MDBs and MDEs,
table documentation includes an estimate of table size. This
information appears a new Table List Report, as well in reports
that show table record counts.
- The Table Index
Properties report displays the index field names along with its
Error, Suggestion, and
Performance Issue Detection
- For forms and reports
without a RecordSource, previous versions of Total Access
Analyzer listed separate errors for every bound control. This
version consolidates these errors into one error, which notes
that the form or report has no RecordSource, and lists the
number of bound controls.
- Relationship errors
due to invalid fields, foreign table fields, and foreign tables
are flagged separately. Previous versions of Total Access
Analyzer listed one generic error for the relationship.
- Table and query names
that contain characters that conflict with SQL Server.
Errors, Suggestions and Performance Tips
and improve your database. Detect unused tables and queries, broken
references, corrupt objects, command buttons that do nothing, forms
controls without default tab order, and
many others. Your database is also examined for ways to improve
its design and performance, and an extensive list of recommendations
Total Access Analyzer
detects over 100 types of errors, suggestions, and performance tips
to help you create Access applications that have fewer errors, are
easier to maintain, run efficiently, and behave the way your users
and you expect.
The analysis is based
on the examination of your entire database looking at each object
and its relationship to others. For instance, the only way to
suggest a query isn't being used is to be able to document all the
places queries are used. The thorough and automated way Total Access
Analyzer examines all your objects, controls, properties, and lines
of code is impossible to replicate manually.
All of your module
code is painstakingly examined for errors and improvement. Unused
variables, unreferenced assigned variables, procedures that should
be private, modules that don't require variable declarations,
missing error handling, type cast omissions, unused labels, and much
cross-reference information shows where tables, queries, forms,
reports, and macros are used throughout your database. This category
contains several reports for flexible sorting and grouping.
field cross-reference reports show where fields from tables and
queries are used in other objects. Various sort options are
available. Field cross-reference information is in its own category
with its own reports because of the large amount of field references
that exist in a typical database.
References, Sorted by Table Name" report shows where fields are
used, and is sorted by the referenced table and field names.
are available listing fields referenced by the calling object.
There is a report for all objects that reference fields, and other
reports for just query, form, and report references.
Module cross-reference category has the most extensive collection of
reports. These reports are available if you selected "Generate
Module XRef. The data is based on detailed analysis of your general
module code and the modules behind the selected forms and reports.
reports are similar to the items available on the Module XRef tab in
the Documentation Explorer (see Module Cross-Reference for more
Summary" reports show the number of lines, procedures, variables
and various other summary statistics for each module.
provides a one page summary for each module showing its public and
private interfaces with their procedures, properties, events,
enums, user defined types, library declarations, implemented
classes, and public variables. Class properties are shown as
ReadWrite, ReadOnly, or WriteOnly depending on whether the
corresponding Get and Set/Let statements exist.
reports show a list of procedures defined in each module with
information on their settings: procedure type, parameters, return
type, etc. You can even include the comments of a procedure. The
comments come from the comment block immediately before your
procedure definition, or if there is none before it, the comment
block immediately after the definition. This provides an excellent
way to track each procedure's purpose.
Sorted by Procedure Name" provides an alphabetical list of
procedures and where they are defined. This is useful as a lookup
when you know a procedure name, but not where it is defined.
– Where Procs are Called From" is the procedure cross-reference
showing where procedures are called from and the parameters used.
This is ideal for reviewing procedure calls before making
modifications to your code.
Called, Non-Event Procedures Only" shows the procedure
cross-reference for procedures excluding event procedures in
forms, reports, and class modules.
"Procedure Calls –
What Each Procedure Calls" shows a list of procedures called by
Declarations" reports show all uses of the Declare keyword to
access external DLL or EXE procedures.
list every enum definition and its members. Reports also show
where they are used.
show events defined by module, and where they are raised.
Type" reports list every user defined type and its elements.
Reports also show where they are used.
reports show a list of variables declared and their data types.
References" reports show where variables are referred to or
assigned values (these reports may be very large).
Constants" reports shows all constants defined, their assigned
values, and scope.
Class Module" reports show variables based on class modules and
where they are defined.
Implements" reports show what classes are referenced via the
IMPLEMENTS command and, for each class, all the places they are
There are also
reports for Line Labels, Access/VBA function calls, DoCmd calls,
and DefType statements.
are the highest level of analysis generated by Total Access
Analyzer. Three diagrams are available for MDBs: Application, Data,
and Object. (Only the Application diagram is available for ADPs).
The diagrams are described in detail for the Documentation Explorer
(see Diagram Descriptions for more information).
reports differ from the view of the diagrams in these ways:
All branches are
object's module type and name is shown.
There is a [See
Num] field for objects whose calls were drawn earlier in the
diagram. The value in the column refers to the line number where
the original drawing is located.
Lines are not
drawn between root level objects.
After you generate your documentation, you can easily search the
results for any string. Easily find text hidden across object
properties and code.
The generated documentation can be viewed on screen using the
Documentation Explorer. Organized in a treeview, you can easily see
information for the entire database, by object type, individual
objects, or the same property across multiple objects.
Extensive options are available when printing reports, allowing
you to customize your output for your needs, or your client’s needs.
You can specify headers and footers, printing format, date/time
format, heading colors, and a variety of module printing options.
Because Total Access Analyzer contains so many reports, getting
the right set for your needs might take time. Because of this, Total
Access Analyzer includes a Report Sets feature. The product ships
with several pre-defined sets that make general report
selecting and printing a snap, including:
Summary: High-level summary reports of all documentation
Structure and Schema: Information on tables and relationships
Cross-Reference: All object cross-reference reports
Improvements: Common things to look for to improve your
In addition, you
can create your own customized reports sets that vary by project,
client, or development team.
the main features of Total Access Analyzer is its ability to
completely document all aspects of an Access database project. The
documentation provided is invaluable for:
current implementation documentation during development: great
for seeing where you are during and Access development project.
Analysis: Ensure that all object names conform to your
organization’s standards as you do development.
Documentation: Provide the end user, client, or customer with
complete structure documentation after your project is delivered.
The demo programs let you explore how Total Access Analyzer works
and the output it generates. It includes documentation of the sample
database SOLUTION.MDB included with Access. With this demo, you can
see the large variety of results generated by Total Access Analyzer,
including view forms and 225+ reports. Click on a link below to
download the demo of your choice.
Access 97 Demo
Access 2000 Demo
Access 2003 Demo
Total Access Analyzer for Access - Single
(Choose Access version)
Per Access Version
Total Access Analyzer for Access - 5 User
(Choose Access version)
Per Access Version
Total Access Analyzer:
Powerful reporting and analysis tools
Complete documentation for all aspects
of Access database projects
Pentium processor or better
Windows 98, 2000, ME, or NT 4.0
20MB available hard disk space
64MB RAM (128 recommended)
Access 2002, 2000, 97 or 2.0