Jump:

Search:

Microsoft Access Developer Center

Strategic Overview

Microsoft Access within an Organization's Database Strategy

How many simultaneous Microsoft Access users?

Blaming Microsoft Access instead of the Developer

Microsoft Access vs. Excel

Best Practices

Taking Over Legacy MS Access Databases

100+ Performance Tips

Winner of Every Best Access Add-in Award

Split Database Architecture for Multiuser

Favorite Features Added After MS Access 2003

Table Design

Designing Primary Keys

Field Type Consistency

Table Normalization Tips

Taking Time into Account

Transposing Data

Set AutoNumber Starting Number Other than 1

Avoid Unnecessary or Duplicate Indexes

Query Design

Form Design

Form Tips and Mistakes

Form Navigation Caption

Using a RecordsetClone

Synchronize Two Subforms

Late Bind Tab Subforms

Subform Reference to Control Rather than Field

Tab Page Reference

Combo Box Top Tips

Properties and Validation

Select First Item

Cascading Combo Boxes

Zip, City, State AutoFill

Report Design

Suppressing Page Headers and Footers on the First Page of Your Report

Add the NoData Event

Annual Monthly Crosstab Columns

Design Environment

Adding Buttons to the Quick Access Toolbar

Collapsing the Office Ribbon for more space

VBA Programming

Using Nz() to Handle Nulls

Avoiding Exits in the Body of a Procedure

Setting Module Options

Math Rounding Issues

Source Code Library

Royalty Free VBA Modules

VBA Error Handling

Error Handling and Debugging Techniques

Error Number and Description Reference

Basic Error Handling

Pinpointing the Error Line

Performance Tips

Linked Database

Visual Source Safe

Deployment

Prevent Close Box

Disable Design Changes

Broken References

Simulating Runtime

Missing Package & Deployment Wizard

System Admin

Disaster Recovery Plan

Compact Database

Compact on Close

Database Corruption

Decompile Database

Bad DLL Calling Convention

Converting ACCDB to MDB

Cloud and Azure

Cloud Implications

MS Access and SQL Azure

Deploying MS Access Linked to SQL Azure

Additional Resources

Microsoft Access Help

MS Access Developer Programming

More Microsoft Access Tips

Technical Papers

Microsoft Access Tools

Connect with Us

Email Newsletter

Developer Team Blog

Don't Deliver a Microsoft Access Database With Broken Object References

Provided by: Dan Haught, FMS Executive Vice President

Broken references are one the leading causes of Microsoft Access database application errors. To avoid these, make sure your queries, forms, reports, macros and module code refer to objects that actually exist. It seems simple, but as you develop your application, add new objects, rename existing objects, and delete objects, your references will be broken. This also happens with module code that references functions in queries or macros. Additionally, if you reference external components through VBA, what works fine on your computer may not work on your user's system. Microsoft Access does not warn you about these problems, so they lurk deep in your application until your user discovers them.

Total Access Analyzer performs detailed cross-reference analysis for all your tables, fields, queries, forms, reports, macros, and module code to verify these references. Avoid the cost, embarrassment, and the loss of trust associated with broken references. While Total Access Analyzer cannot detect every issue that could potentially happen, it goes a long way towards helping you ship zero-defect applications.

Total Access Analyzer performs the analysis to detect inconsistent field data types and sizes for all your fields. So whether numeric fields or the size of text fields differ, you can easily catch such structural flaws.

Feedback

Contact Us l Web questions: Webmaster l Copyright © FMS, Inc., Vienna, Virginia
Celebrating our 26th Year of Software Excellence