View Single Post
  #2  
Old May 5th, 2010, 05:53 AM posted to microsoft.public.access.tablesdbdesign
Rick Gould
external usenet poster
 
Posts: 2
Default System for Analyzing a database

There are a few things you can do. The best one for me is to find an easy to
talk to user who uses this database. Spend 15 to 30 minutes with them
watching them use the database. Ask them which screen and reports they use.
From their I create a quick drawing document showing the screens and the data
they use, specifically the queries and tables.

Most databases I inherit have numerous queries that are not used anymore,
and, do not even reflect the current linking structure of the database. I
never rely on the queries by themselves to tell me what is going on in a
database - start from what is "really" happening.

If I don't have ready access to a user then I look through the forms to find
what I consider is the main one and go from there, again following into
subforms, queries and tables.


"TGalin" wrote:

I am working with an access database that I did not create and I am looking
for pointers that will help me analyze and understand what is happening with
the data as it is being transferred between tables. More specifically, I
need to figure out what the database queries are filtering and manipulating
as they transport the data to its final table output. I know exploring the
queries in design view will help, but choosing where to start seems confusing
and I am seeking, if possible, a more step by step/sequential approach to the
undertaking. Do you have any suggested approaches or strategies that might
help me accomplish this task more effectively?