 There are 50 reports available in Total Access Inspector 2000. This section provides examples of a few of the key reports so you get a better feel for the type of output it generates and how it can help developers achieve Year 2000 compliance in their Access databases. The reports are organized to provide top-level, summary information, detailed lists of detected issues, and support information to detect additional issues (e.g. data analysis), simplify fixing the detected issues, and verifying the issues are fixed. The sample reports included are based on the analysis of the Northwind sample database that comes with Access 97. Although Northwind is a relatively simple database, it has hundreds of Year 2000 issues and areas where dates are used. |
 |
Summary Report (Sample)
This Executive Summary Report reveals your database's exposure to potential Year
2000 problems. This report provides a broad overview of the types of issues found and in
which objects they exist. In particular, the Object Analysis, Field Analysis, and Form and
Report Control Analysis sections guide you to those parts of your application that need
further examination.
Summary of Issues by Object
An overview showing the
severity of Year 2000 issues for each object and where you need to focus your efforts.
Number of Issues Found
See by risk category, each type of issue detected and the number of occurrences
of each. This overview is helpful in determining the types of problems a database has and
how to address them.
Issues Found Detail
Detailed listing of each
Year 2000 and date related issue with the issue found and where. Several sorting options
are available to simplify your compliance efforts.
- Sorted by Object and Property (Sample)
- Sorted by Issue (Sample)
- Sorted by Object and Issue
- Sorted by Risk and Issue (Sample)
- Sorted by Risk, Object, and Issue (Sample)
Issues By Risk Category
Each issue is classified into one of three risk categories. Detailed listing of
issues grouped by risk category are available.
- High Risk (Sample)
High Risk issues are almost certain to cause Year 2000 problems in your application. For example, if the InputMask on a form control requires a two-digit year input or dates with two-digit years are displayed, the object is not Year 2000 compliant. Total Access Inspector 2000 flags the issue as high-risk. This reports shows all high-risk issues detected in your database. - Moderate Risk
Moderate Risk issues indicate dates or potential dates are being used. These issues may or may not have Year 2000 problems, but need to be checked to verify dates with four-digit years are being used. For instance, the use of the Year command or a caption with date text may be flagged. Although these are not Year 2000 problems, they indicate dates are being used, so you need to examine these objects and related objects/code to verify dates are used correctly. - Unknown Risk
Unknown Risk issues are items that may or may not be date related and usually involve external files that are imported or exported. It can also include ActiveX controls, VBA library references, and Clipboard and SendKeys commands. Examine these items to see if they use dates, and verify any dates are passed and manipulated correctly.
Table Field Analysis
The Table Field Analysis reports provide information about every field in your
application. These reports expand on the Field Analysis section of the Summary Report.
Using these reports, you can quickly see the fields in your database storing date data, as
well as fields that potentially contain date data but are not Date/Time fields (e.g.
month/year fields, text fields from mainframes [MMDDYY], year fields, etc.). The minimum
and maximum values of each field is also shown to help you identify bad data.
- All Fields (Sample)
- Date Fields Only
- Potential Date Fields Only
Query Field Analysis
Similar to Table Field Analysis, the output fields of queries are listed to see
which queries expose Date fields.
- All Fields
- Date Fields Only
- Potential Date Fields Only
Field Cross Reference
After determining which fields have date information, you need to know where they
are used. The Field Cross-Reference reports reveal where each field is used across the
other queries, forms, and reports. Use this as a guide for verifying dates are properly
used.
- All Fields (Sample)
- Date Fields Only
- Potential Date Fields Only
Form Control Analysis
Because data entry and data viewing are often handled by forms, how your forms
handle dates is critical for Year 2000 compliance. The Form Control reports are designed
to help you implement those recommendations. The Form Control reports reveal the primary
properties (ControlSource, InputMask, Format, Validation Rule, and Validation Text) of
every control on every form. This report makes it easy to verify consistency across the
controls on a form and across multiple forms. If a control has date issues, it is flagged.
- All Controls (Sample)
- Date Controls Only
Report Control Analysis
Similar to the Form
Control Analysis reports, you can see all the controls on a report and verify date format
settings are correct.
- All Controls
- Date Controls Only
Macro and Module Printouts
For complete Year 2000 compliance, someone may need to manually examine every line of
code, especially lines around flagged issues. These report will help that person.
- Issue Lines in Context (Sample)
All module lines are shown with the lines where issues are found preceded with a bold label listing the issues. - Issue Lines Only, Sorted by Issue
- Issue Lines Only, Sorted by Module Type and Name
- All Lines
External References
Examine external objects used by the database including ActiveX/OCX controls,
linked databases, VBA libraries, DLLs, external files, and spreadsheets. These objects may
or may not use dates, but need to be verified that any dates they use are properly
handled. The list of objects and where they are used are provided.
- Sorted by External Object Type
- Sorted by External Object Name
- External Object Cross-Reference, Sorted by Calling Object (Sample)
- External Object Cross-Reference, Sorted by External Object
Issues Detected
List of the issues Total Access Inspector 2000 attempts to find. The list can
include the built-in rules and search strings, and additional strings supplied by the
user. Of course, not all issues are found in each database.
- Sorted by Issue (Sample)
- Sorted by Risk
Exclusion Words (Sample)
To reduce the number of false hits, you can exclude words from the detection
process. For instance, Update events are not flagged as date related even though
"date" is part of the word.
