Microsoft Access Developer Center

Table Design

Query Design

Form Design

Form Tips and Mistakes

Module VBA to Forms and Controls

Form Navigation Caption

Using a RecordsetClone

Synchronize Two Subforms

Multiple OpenArgs Values

Late Bind Tab Subforms

Subform Reference to Control Rather than Field

Tab Page Reference

Shortcut Keys


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

Basics: Forms and Controls

Using Nz() to Handle Nulls

Avoiding Exits in the Body of a Procedure

Shortcut Debugging Keys

Setting Module Options

Math Rounding Issues

Rename a File or Folder

Avoid DoEvents in Loops

Age Calculations

Weekday Math

Sending Emails with DoCmd.SendObject

Source Code Library

Microsoft Access Modules Library

Microsoft Access 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

Subdatasheet Name

Visual SourceSafe

Deployment

Runtime Downloads

Simulating Runtime

Prevent Close Box

Disable Design Changes

Broken References

Remote Desktop Connection Setup

Terminal Services and RemoteApp Deployment

Reboot Remote Desktop

Missing Package & Deployment Wizard

Avoid Program Files Folder

Microsoft Access Front-End Deployment

System Admin

Disaster Recovery Plan

Compact Database

Compact on Close

Database Corruption

Class Not Registered Run-time Error -2147221164

Inconsistent Compile Error

Decompile Database

Bad DLL Calling Convention

Error 3045: Could Not Use

Converting ACCDB to MDB

SQL Server Upsizing

Microsoft Access to SQL Server Upsizing Center

Microsoft Access to SQL Server Upsizing Center

When and How to Upsize Access to SQL Server

SQL Server Express Versions and Downloads

Cloud and Azure

Cloud Implications

MS Access and SQL Azure

Deploying MS Access Linked to SQL Azure

Visual Studio LightSwitch

LightSwitch Introduction

Comparison Matrix

Additional Resources

Microsoft Access Help

MS Access Developer Programming

More Microsoft Access Tips

Technical Papers

Microsoft Access Tools

Connect with Us

Email NewsletterEmail Newsletter

FMS Development Team BlogDeveloper Team Blog

Facebook PageFacebook (Feed)

Twitter with FMSTwitter

FMS Support SiteSupport Forum

 

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

Provided by FMS Development Team

Broken references are one the leading causes of Microsoft Access database application errors. Someone opens a form and the underlying table or field is missing causing the whole application to crash. This often occurs when the object was renamed or deleted and the objects referencing it weren't updated.

To avoid such mistakes, 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, references become 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.

Automated Process for Quality Assurance

You can manually verify everything in the database is working properly but that's challenging and time consuming to do as projects get larger.

Our Total Access Analyzer product automates this and performs detailed cross-reference analysis for all your tables, fields, queries, forms, reports, macros, and module code to verify references are valid. 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 along with hundreds of other issues to improve the quality of your Microsoft Access solutions.