DSmith, what do you mean by "unable to use the object dependencies"?
Turning on the Name AutoCorrupt setting Brendan referred to should enable
the feature, but please do this in a *copy* of the database that you don't
mind destroying, and whether you can "use" it might be a matter of
definition.
I tried this in an old database that was known to have queries and forms
that referred to tables that no longer existed. I coded up a solution to
list the bad dependencies, but found that Access just kept crashing (shut
down by Windows.) I never did get the code to run to completion. After
several dozen crashes, recreations of the database (and restarts), I
concluded that this "feature" was completely unusable, at least as a way of
tracing bad dependecies.