How do you find which Objects are called by other Objects

[Greg]

I have an Access database which has a number of tables,
queries, forms, macros etc.

If I want to make some changes to a particular query,
macro or subform, is there a way to find out which other
Forms, Queries or Macros call the object I want to make
changes to.

For example, is there away to search through all objects
to see if it calls a particular object whose name I
specify?

The situation is that I want to make some changes to an
underlying query attached to a particular field in a
particular form. I want to know if I make these changes,
will it affect any other forms or queries.

 

[John Nurick]

Hi Greg,

One of these utilities:

Speed Ferret www.moshannon.com
Find and Replace www.rickworld.com
Total Access Analyzer www.fmsinc.com

 

[John Vinson]

For example, is there away to search through all objects
to see if it calls a particular object whose name I
specify?

There's nothing builtin to Access to do this, but some third parties
have filled the gap:

Freeware: http://www3.bc.sympatico.ca/starthere/findandreplace
Find and Replace: http://www.rickworld.com
Speed Ferret: http://www.moshannon.com
Total Access Analyzer: http://www.fmsinc.com

(in increasing order of cost and power/complexity)

 

[Craig Alexander Morrison]

Actually John, Access 2003 has introduced the Object Dependencies feature
(it does not work on ADPs though).

If one is using Access 2003 all one need do is right click on the object and
select Object Dependencies, it could do with a bit more work, but quite
useful.

A nice feature of the Object Dependencies list is that you can click on a
object in the list and open it in design mode.

The list can be either "Objects that depend on me" or "Objects that I depend
on".

--
Slainte

Craig Alexander Morrison

 

[tina]

i tried that out. unfortunately, i got the following message:

To generate object dependencies, the Track name AutoCorrect info option must
be turned on.
Enable name AutoCorrect and continue?
OK Cancel Help

the AutoCorrect feature causes a lot of problems, which have been discussed
here in the newsgroups and documented in the MS Knowledge Base. it's always
the very first thing i "turn OFF", when i create a new database. i'd
hesitate to turn it back on, even briefly, for any reason.