This report answers the critical question:
Where are my Microsoft Access table fields used and referenced?
This powerful report shows where and how each field is defined or referenced across the entire database. Knowing where your fields are used is certainly important before changing them.
In this example, the data is sorted by field name (Address, Birth Date, CategoryID). Within each grouping, you can see where the field is used. For instance, the Address field is used in a Query named Invoices, which is used by a control in the Invoice Report.
The data shown here is similar to the Table References, Sorted by Table Name, but it's sorted by Field Name to show all the tables where identically named fields are used. This is a great tool for verifying consistency of field definitions. A good programming practice is to make sure identically named fields are defined the same way (same data type, data size, and description)
Here's the complete list of the Total Access Analyzer reports documenting the tables in your MS Access database. Click on the hyperlinks for more information. Rather than overwhelm you with every report, we've provided a subset of the most interesting reports for you to review. The others show similar data but use different sort orders or filters.
Simple lists to gain a quick understanding of all the tables in your database and their relative size
Examine fields lists for each table, or for each field which tables its in, along with their properties
Look at all the properties of a field the way you would in the table designer or see a property value across all the fields that have them.
Examine indexes and their fields and properties
Detailed listing of each table, its properties, indexes, fields, etc.
Version 16.7 for
Microsoft Access 2016
Version 15.7 for
Microsoft Access 2013
Version 14.7 for
Microsoft Access 2010
Version 12.97 for
Microsoft Access 2007
Version 11.95 for
Microsoft Access 2003
Version 10.8 and 9.8 forr
Access 2002 and 2000
"Total Access Analyzer is an amazing product that I've relied on and recommended for years. It's a huge time saver."
Sal Ricciardi, Programming Writer, Microsoft Corporation