Thank you! Thank you!
I just finished reading this
document, which was part of a link in the
recent Buzz newsletter. I have printed it for others to read, especially
those skeptical on the powers of Access and its capabilities.
Darren D.
|
|
Don't Deliver a Microsoft Access Database With Broken References
Provided by: Dan Haught, FMS Executive Vice PresidentBroken 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.
Return to the tips page
|
|
