One thing that really helps with the documenter is to open up the properties sheet and UN-check MOST options.
For example, you get “pages” of material for one table, but if you uncheck all options, say like this, then the resulting output is FAR more useful.
So you can “massive” reduce the volume of the documenter. And these days, I not really sure if you want to use paper or a PDF, as you can simply use the Application as the reference document anyway.
And don’t forget the dependences view. This gives you a tree view of all objects, and you can “drill down” the dependencies. So what forms, reports, tables and even quires are involved in a SINGLE query can be viewed.
This amazing (but little used) feature looks like this:

The above gives a GREAT “overall” view of objects in the database and does so via a fluid UI that allows one to inspect a given object, and dependences. And you can click to open + view the objects in design mode right from that treeview. In effect you can
“surf” the whole project with dependences. And note how even a query based on a query etc. can be observed.
A “large” printout does little to document a single object and the “very” important dependences. I “much” agree with your point about creating large volumes of documentation does little to help your goal here.
The above "dependency" view is perhaps the best unknown tool in Access that gives the developer a “view” of the application. In fact I wish other development systems had the above feature!
Regards,
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada