You can test it on a *copy* of the database, where it doesn't matter if it
gets messed up.
Name AutoCorrupt is a very good way to confuse Access about what you are
referring to, and introduce corruptions. I don't even bother trying to keep
this list up to date any more as the problems are legion, but it should be
enough to give you the picture:
http://allenbrowne.com/bug-03.html
In terms of the Object Dependency stuff offered in A2003, I gave this a try
too. The purpose was to identify the queries, forms, and reports that
referred to tables that no longer existed, or fields that were no longer in
the tables. It turned out that the dependecy stuff was not about to cope
with these missing objects. We coded up a routine to walk the objects and
trace the dependencies, but we never did get it to run to completion. Access
2003 repeatedly crashed (shut down by Windows), leaving the impression that
the dependency stuff was hollow.
