|
||
|
Microsoft Access 2010
Version
X.9 Versions
X.8 Versions Analyzer Info:
Best Practices (Errors, Suggestions, and Performance Tips) Finding Unused Objects and Code
Why Analyzer?
"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 Additional Info:
|
More information on Diagram Displays and Reports Errors, Suggestions, and Performance TipsTotal Access Analyzer detects a wide range of issues to help you create better Access applications by flagging items that will cause it to crash, and offering suggestions to improve your application and performance. A list of issues detected is available here. Error ReportsErrors are problems that will most likely cause your Access application to crash. For instance, references to objects that were deleted or renamed crash when the user encounters them. When Total Access Analyzer detects these errors, you should examine them carefully and fix them before deploying your database. Suggestion ReportsSuggestions incorporate our knowledge of Best Development Practices for creating professional Access applications. Suggestions cover items that are not necessarily going to cause your application to crash or perform poorly, but may make it easier to maintain, support, and appear more polished. For instance, we may note that certain objects or code are unused, but that doesn't mean you have to delete them. Most suggestion reports are lists of issues. These two powerful reports are the results of analysis that you should review them to determine next steps: Performance TipsPerformance tips are ideas where you may be able to enhance the speed of your application. Certainly, many tips are not relevant because you've already implemented the most efficient solution. Nonetheless it's helpful to consider these ideas or objects that may be made more efficient. Module AnalysisModule PrintoutsTotal Access Analyzers offers two reports to print your modules. The first is the standard display of your code as is, the second formats your code to indent the logic loops and show brackets around loops and exit arrows from them:
Module VBA Code Analysis
Plus many other reports on module contents such as VBA functions, labels, variables, DoCmd, constants, compiler conditions, etc. Basic DocumentationThere are a large number of reports for each Access object type. Here are some examples. Form and Report BlueprintsQuickly see what each form and report looks like with each control annotated:
Table Documentation
Query DocumentationForm DocumentationReport DocumentationMacro Documentation
Additional ReportsMany other reports cover these areas:
for more information, visit the Entire list of reports available in Total Access Analyzer |
![]() |
Contact Us
l Web questions: Webmaster
l Copyright
© FMS, Inc., Vienna, Virginia |