Verifying Consistent Definitions of Identically Named Fields

A fundamental Best Practice of database design is to make sure identically named fields represent the same data and are defined the same way (same data type and data size).

Assuming you want to do this, it's important to verify identically named fields are defined the same way. Failure to do this could cause data loss (truncated data) as information moves from one table to another.

For instance, a FirstName text field should always be the same length anywhere it's defined. Not 30 characters in one table and 50 in another. Similarly, a numeric CustomerID field should not be an Integer in one table, a Long Integer in another, and a Double in another.

Field Consistency Analysis

As part of its analysis, Total Access Analyzer examines all the fields in your database, compares identically named fields in multiple tables, and flags the field names that are not identically defined. If it finds any, the results are presented in the Suggestions report: Table Fields with Different Types.

The report shows for each field with an inconsistency in Data Type and Size, all the places where the field is defined. You can then determine if and where you need to make the changes.

In this example, you may want to change the City field from a size 40 to 50 in the tblCustomer table, and modify the Comments field in the IncidentItems table from a Text to Memo: