I have developed what is (for me) a fairly complex report, with a number of
fields that are not visible, but are necessary to the report's functioning,
and some programming On Print and On Formatting.  Depending on the data, the
report looks different.  

I'll be moving on in June.  They should replace me with someone trained in
Access, ideally much better trained than I am.  However, there's a good
likelihood that that may take a year or two.

I'd like to leave behind something that explains how this report works, so
that someone trying to adjust it to changing realities in years to come can
do so, particularly if they are not so well skilled in Access that they can
do better rewriting it from scratch.

I've got comments in the programming, but has someone got some suggestions
about good ways to document what is going on in a report design?

Actually, any tips on how to leave records that explain what is happening in
a database as a whole would be helpful.  An expert will be able to backtrack
it, but how do I tell some future novice what I did?  Which kinds of things
are they likely to need to know?  Probably too broad a question, but maybe
you have a pointer or two you could give me.

Thanks.