untangling parallel dependent queries

[Glen]

Hello,

sorry for the obscure subject, but it's the best I could do.

I have a database that has a lot of dependent queries. I've tried to name
the queries to indicate dependencies eg:
qry01_.... are base queries
qry02_... will have dependencies on 01 queries
....
qry08_... queries will have at least one 07 query that they are dependent on.

There are about 50 queries in total, which take a finance dataset and an
asset register dataset and eventually combine them in a big crosstab.

A while ago, I reworked the queries, making some redundant by writing new
queries. However, I didn't delete the redundant queries as I wanted to leave
them in case I needed to go back to them, and it didn't occur to me to add a
flag to their name.

So, I now have some queries that I'm pretty sure are redundant, but can't be
sure due to the fog of time. Is there a simple way to report on these
dependencies? Maybe a table with query names across the top and dependencies
listed underneath?

Also, if anyone has a better naming convention for indicating dependency,
I'd appreciate any pointers.

Thanks in advance,

Glen

 

[John W. Vinson]

So, I now have some queries that I'm pretty sure are redundant, but can't be
sure due to the fog of time. Is there a simple way to report on these
dependencies? Maybe a table with query names across the top and dependencies
listed underneath?

There are some good third party tools for this:

Free: 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