Database Map

[Guest]

I am currently working for a company on a short term contract. Before I leave
I have been asked to document the database so the realtionship between forms,
queries, macros and reports can be seen.

I have also been asked that I remove anything from the database that is not
being used. There are a lot of queries that aren't useful anymore due to
changes i have made to the database. I have also made a lot macros redundant
andthese aren't as obvious to me. I have tried documenter but it doesn't
always work and it doesn't make the relationships clear enough.

I was hopingthat I could map the relationships with a simple flow chart
displaying the report, query, table, form and macro names so that I could see
how they relate to each other and if there was anyhting I could remove.

I have begun to work on this and it has been extremely tedious. I would like
to ask if anyone knows of a quick way to do this or any alternative solutions
that would help me display the realtionships betwen them.

Please help me!!!

EliotF

 

[Larry Linson]

If you are interested in chasing down all the references to each of the
object, two products often recommended are Speed Ferret,
http://www.moshannon.com and Find and Replace, http://www.rickworld.com. The
last version of Find and Replace that I used was for Access 2.0, but I have
used recent versions of Speed Ferret and been pleased.

If you want more "depth" that might save you some time, but at higher cost,
check out the products of FMS, Inc. at http://www.fmsinc.com -- they were
one of the first producers of Access utilities.

MZ-Tools, http://www.mztools.com, has several utilities, some freeware that
you might find useful. Being frugal-minded, I'd probably look there first.
<GRIN> Actually, I'd look at all of these, and try to pick the one that was
the best fit for what I want to do.

When I had to document a very large database system in 2000, I primarily
used locally-created queries and Speed Ferret -- the database was in Access
2.0 and was sufficiently large that tools with more "breadth and depth"
would freeze (only run partway, then stop because of memory and other
resource limitations). [Some | Most | All] of those limitations do not
plague later versions of Access.

Larry Linson
Microsoft Access MVP