David, the Object Dependencies don't work reliably in Access 2003 either.
The feature relies on Name AutoCorrect, which is guaranteed to get Access
confused between the field names, captions, and aliases, past and present.
It is probably the most prominent cause of corruptions during database
development. If it wasn't serious, it's kinda amusing to see Access mistake
the alias on a calculated query field for one of your field tables, just
because you used to use that alias name in the Caption property of the field
at some time in the past.
Back when A2003 was first released, a client handed me an old database that
had hundreds of queries, forms, and reports that referred to tables,
queries, and fields that no longer existed, so I converted a copy to A2003
to see if the dependency routines would help me pin these down. The syntax
was easy enough to master, so I soon had a routine to walk the objects and
identify the problems. Compile. Save. Execute. Crash (i.e. Access shut down
by Windows.) After a couple of hours of repairing, setting different
starting points, trying different types of objects, we just gave up. The
simple code never did run to completion.
I don't bother keeping this page up to date will all the problems associated
with Name AutoCorrupt any more because there are too many of them, but this
will at least give you a taste for it:
Failures caused by Name Auto-Correct
at:
http://allenbrowne.com/bug-03.html