Clarify/improve output of MS-Access Documenter tool

C

Charles Duby

Two problems when using the tool for documenting macros:

1 - The source DB application file, printed at the top of the page, is
truncated when it is long, which is typically the case when working in a
large, networked environment.

2 - Unless the user has placed the name of the macro in a comment field,
Documenter does not print the name of the macro. So you might get 5 or 6
printed pages, which, when examined a week or so later, cause one to say,
"What the heck is this?" It's especially difficult when to sort out what is
when documenting multiple DB objects in one run.


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-8f4a-1a4841541580&dg=microsoft.public.access
 
A

Albert D.Kallal

2 - Unless the user has placed the name of the macro in a comment field,
Documenter does not print the name of the macro.
Click to expand...

Hum, I just checked, and the name of the macro is printed at the top of each
page. I wonder if your problem is related to the "large"/long path name.
 
P

Pete

I can recommend FMS Total Access Analyser as not only does it produce
excellent documentation it is also very good at finding omissions and errors
in your code.
 
Top