Thank you for making Total Access Analyzer the most popular Microsoft Access add-in program of all time. With the release of Total Access Analyzer for Microsoft Access 2013, we've created an update for Total Access Analyzer for Microsoft Access 2003. Version 11.95 replaces version 11.90 and includes new features and improvements based on our experiences and customer feedback.
We've made many enhancements since version 11.90:
Documentation was enhanced to:
New reports are available to see, by control type for forms and reports, how many and where they are used in your project. The new reports include:
For more information, visit Control Type Reports.
Total Access Analyzer performs module analysis and cross-referencing to identify invalid procedure calls. If your database calls functions stored in a library, those functions are not being detected and procedure calls to them are incorrectly flagged as undefined.
Total Access Analyzer cannot detect the procedures in your referenced library databases. However, if you create a table in your database listing the procedure names from your library or libraries, Total Access Analyzer will avoid flagging those procedure calls as undefined.
Simply create a table name usysTAnalyzerLibraryProcs in your database with two text fields: Procedure and Library. Fill the table with the procedure names you call. The library value isn’t required, but provided for easier tracking. Total Access Analyzer will check the list to avoid identifying those procedures as undefined.
Over the years, from customer feedback and as we encounter mistakes in our own work, when possible, we add their detection to Total Access Analyzer. This version includes three new Best Practices:
DECLARE statements let you use procedures defined in DLL files and Windows API commands. Procedures defined in DECLARE statements that are not called are flagged as unused.
Parameters shouldn’t be the same name as the property or procedure name since it creates confusion when referencing it.
Previously, all of these unused definitions were categorized into one Unused Variables group. They are now separated into three separate issues so you can manage them differently. Unused Parameters are particularly important to address because the calling procedure may be expecting different behavior from the procedure based on that parameter, but it’s completely ignored.
The VBA module parser for the 11.90 version added support for compiler conditionals in the declarations section or procedures as defined in #IF...#ELSE…#END IF statements. This is particularly common when using the VBA7 constant to manage 32 versus 64 bit code:
#If VBA7 Then < 64 bit specific code > #Else < 32 bit specific code > #End If
The VBA parser in version 11.95 supports entire procedures defined by compiler conditionals to avoid triggering duplicate procedure definition issues. The duplicate procedures should be paired together:
#If VBA7 Then Sub ProcName() ... End Sub #Else Sub ProcName() ... End Sub #End If
Conditional compilers are also considered when determining unused code.
A search bar, similar to what’s available on the Navigation Pane, is added to the places where you select objects.
This simplifies the filtering of the list of objects by name.
The list of documented databases now shows when each database documentation process started and how long it took.
In addition to the report listing the databases by name, two new reports are available:
For the reports that show issues, you can specify a filter to limit which issues are included. The Errors, Suggestions, and Performance tabs now show the count for each issue to make it easier to decide which issues to include:
The Count Field is Added to the Report Filter for Issues
When viewing module results, the Module Tab now shows the entire module rather than separate records for each procedure
When viewing module results, you can press the Design icon to open the module editor at the current procedure. This feature is enhanced to better handle property Get, Let, and Set definitions, and to move to the first line of the procedure (after any comment lines) and highlight it.
With higher and higher resolution monitors, larger fonts are used throughout the program to make it easier to read.
Updated manual and help file with detailed documentation of how the program works and how to best use it.
Due to the differences within each version of Microsoft Access, there is a separate version of Total Access Analyzer for each version of Access.
Total Access Analyzer Pricing
by Microsoft Access Version
|Microsoft Access Version|
|Single||$299||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now|
|5-Seat||$899||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now|
Upgrade Between Access Versions
|Single||$199||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now|
|5-Seat||$599||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now|
Update to the Latest Release within the Same Version
|Single||$149||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now|
|5-Seat||$449||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now||Buy Now|
Premium Support Subscription
Also available as part of
Total Access Ultimate Suite
Total Access Developer Suite
|Total Access Analyzer is licensed on a per user basis.
Each user who runs the program must have a license.
Read the License Agreement for details.
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