How to print Map or Schematic diagram of our database ?

[Mel]

We want to create a complete map or schematic diagram of our database
showing connections between...

Forms, Command Buttons, Queries, Tables, etc Like

frmMenu -->cmdOrders -->: frmOrders --> qryOrders --> tblOrders

frmMenu -->cmdAccounts ---->frmAccts (subFormPeople)
...frmAccts -->qryAccts-->tblAccts
...subFormPeople-->qryPeople--tblPeople

Of course it gets much more complicated to "draw" all the
"connections" is as some queries are used by more than one form and
some forms are used by more than one cmdButton, etc. The
interconnections can make the "schematic" of the database complicated.

This helps as during the design process you may end up with unused
queries and forms, etc.

right now we are doing it by hand... drawing it in PowerPoint... each
table, query & form in a box... with arrows showing dependencies.

Right clicking and asking for dependances forces us to do each object
one at a time... is there a tool to map the whole darn thing?

thanks for any help.

Mel

 

[Susie DBA [MSFT]]

I'd just use MS Paint; and print screen


maybe word?

 

[Mel]

We are currently doing this by hand as we would do with Paint...

But we want to show the "connections" between all the tables, queries,
forms & Command Buttons without having to manually trace them.

We are looking for a detailed schematic of the data base.

A box around each Command Button, Form, Querie & table.

Connecting lines showing...

.... that this Command Button opens this form
.... which gets its data from this query
.... which gets its data from these two tables..

It gets complicated when you have Forms with seveal Command Buttons
and/or subForms, Queries that get data from more than one table,
queries used by more than one form... tables used by more than one
query and forms called by more than one form or command button.

Maybe someone knows of a tool that will do this.

thanks again.

Mel

 

[Guest]

Mel,

That is an extensive diagram you want to lay-out there. I don't know if
there is any form of tool out there that maps all your wishes. Commandbuttons
aren't really objects you can map.

Maybe you can try the object dependencies. Try rightclicking a query and
choose the last option. This might take a few seconds but you'll get an
overview of dependencies in a seperate taskbar. Maybe you can make a
'screendump' of that.

Maurice

 

[Albert D. Kallal]

Visio will help you do this.

for the tables, you have the build in er diagram.

Here is a screen shot of Visio:

http://www.members.shaw.ca/AlbertKallal/Articles/PickSql/Appendex1.html

and, here is a er diagram of the tables in ms-access

http://www.members.shaw.ca/AlbertKallal/Articles/PickSql/Appendex2.html

The 2nd screen shot was done in ms-access, and the tools to do this is built
in.

For forms, and a diagram view, there is not really much you can do, except
build that by hand.

usually, the relationship window is the #1 thing I need.

 

[Mel]

Object dependencies can help provide the data but doesn't do a
schmeatic.
Albert, your suggestions seem to concentrate on function or on table
relationships.

To do this by hand...
draw rectangle for your cmdButton with the title in it.
draw rectanble for the Form it opens with the form name in it
connect the two with a line... arrow pointing at the Form
draw a rectangle for the query from which the Form gets its data &
put the query name in that rectangle
connect the Form rectangle to the Query rectangle with arrow pointing
at the query
draw a rectangle for the table from which the Query gets its data &
name it
connect the query to the table with the arrow pointing to the table

do this for everything in your data base and you have a complete
schematic of your actual database

For forms with subForms draw a larger rectangle so you can put a
rectangle in for each subform.

This is labor intensive but reveals a lot about your database and may
show you objects you created you don't really need anymore... and may
help you clean up your design.

Otherwise you are just remembering all these connections in your head.

After you have a number of tables, queries, forms & CmdButtons the
connections get very fuzzy when you just look at the list in the
Access design window.

Got to be a tool to do this analysis and drawing... doesn't there?

Mel

 

[Larry Linson]

The most extensive third-party documentation tool is Total Access Analyzer
from FMS, Inc.. You can determine whether it meets your needs by visiting
their website http://www.fmsinc.com.

Larry Linson
Microsoft Access MVP

 

[Albert D. Kallal]

Got to be a tool to do this analysis and drawing... doesn't there?

Well, I would not use power point, and as mentioned, tools like Visio are
far better.

The problem here is that labour costs of developing this documenting are FAR
MORE expensive then using the actual mdb file as the source for your
information.

If you need to find out what code a button uses, then you simply go to that
form, open it up in design mode..and look at it. Having that formation on a
diagram, or document does not improve the development process in a
significant way (at least not more then the cost of developing that
documenting).

There is not a UML, or object relationship diagramming tool available for
ms-access. We are talking about a $109 upgrade, or $200 retail product here.
Some of those UML diagram tools cost $20,000 a pop.....

Really, save that money, use it to feed the poor, and get some decent
developers that can find there way around the mess they created....

I am a HUGE fan of using the good tools. #1 on your list is a good data
schemata. once developers have that good data relationships diagram, then
most of the rest will fall into place development wise.

Which would you choose?

1) great code, but bad data designs

or

2 ) bad code, but great data designs?

#2 wins every time. If you have a good data layout, then the code
practically writes it self...

And, if you think there is a market for a diagrmaing tool, then simply grab
the yellow pages, hire some devloeprs, build this diagramming tool, and then
sell it. The yellow pages in my small city has aobut 300 pages of hungray
devlpers waint for work. So, pick up the phone, make the call...and then
sell the tool that you assume every one need. What could be more easy?

 

[Pat Hartman \(MVP\)]

Luke Chung (Mr. FMSInc) should give me a commission for all the times I
recommend this product. I have been using it since Access 97 and it creates
excellent "maps" of dependencies. There are hundreds of reports to choose
from but my favorites are the cross references, object and data maps, and
the form/report blueprints. The blueprint gives you an excellent way to
document forms/reports. It creates a picture of the form/report and
replaces all controls with a number. You can then look at the properties
associated with the number.

 

[Albert D. Kallal]

As a side note, I *am* assuming that you looked at Larry's suggestion

The tools from FMS will give some diagramming.......

You can't modify the results from FMS..but, they will generate a lot of
reports for you...

 

[Susie DBA [MSFT]]

MDB cry baby


'oh, but it's too hard to use sql server'

rofl

your crack addict loser MDB development is obsolete, kid

 

[Tony Toews [MVP]]

Note that this person is really A a r o n K e m p f and that he is not an employee
of Microsoft.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Susie Johnson]

Note that tony is niether MOST or VALUABLE or a PROFESSIONAL

he's a friggin MDB cry baby!

 

[Susie Johnson]

I reccomend SQL Server and Diagrams

they are a lot better than MDB; and it's built in FREE functionality