Tips to document Access program

[Mindy]

Hey, guys,

Thanks for all the help I get from this discussion group. Now I am at
the end of programming.
I want to document my ACCESS program.

Does anyone have tips of documenting ACCESS program? Is flowchart a
good idea? Thanks in advance!

Mindy

[pietlinden]

One way to think of what and how to document is by asking yourself some
questions - along the lines of "If someone handed me this project, what
would I need to make sense of it?" As one of my bosses put it
(referring to an entire network of stuff) - "What is all this and what
does it do/what purpose does it serve?"

If you really want to get a good idea, find a moderately complex
database that someone else built and try to make sense of it. What
questions would you ask this person so that you can update/modify the
database? Answer those and that should be a good start.

[jeremygetsmail]

Also, you'll want to be really clear on the purpose of the
documentation itself. Is it for a user or a developer? If it's for a
developer, is it so that person can get a sense of where various bits
of processing happen, or so that person can dig right in and find
problem areas without having to walk through hundreds of lines of code?

Also, think about tying your comments to error messages that happen in
the code, and debug statements, so you can make that debugging easier.

And, of course, remember to do the documentation at the same time as
you do your initial coding <G>.

Jeremy
--
Jeremy Wallace
Fund for the City of New York

[Mindy]

thank you.

[Mindy]

thank you