[AccessD] is there an app for ththe is?

[Arthur Fuller]

Over manyyears of development, this app contains dozens, perhaps even
hundreds of modules, forms, queries etc. that are no longer used in the
current implementation, Is there a tool that can identify such objects?
Perhaps by date of last call, or something. I'd love  to archive the
current version, then strip it down to only those parts in current use,
then remove all the extraneous stuff and wind up with s  lovely, slender
version.
A few years back, I learned a trick from the inestimable Jim Dettman. Until
I encountered his code, I tended to write "all in one" apps, but Ji showed
me a much better approach that never even occurred to me. Specifically,
reports that ought to run daily or weekly or monthly, for example. Create a
separate FE that does just that one thingl strip it out of the Big App, and
use Scheduler to fire it rather than asking for human intervention Suddenly
EOW, EOM reports just spew from the printer, or are emailed to those
persons of interest and the transactional app is freed from all that
ancillary business, and can focus on its business: transactions, while
little tiny apps can focus on their single task -- to produce a report of
whatever -- sales today, items to order, customers behind in their
payments, etc. -- all managed by the Schedular and requiring no human
intervention.

A bug somewhere? There's one tiny app to examine and fix. No clutter to
wave through (hundreds of objects), just the immediate few of that moment
of interest. Easier to fix, easier to add new ones -- in every case easier

Thanks for that profound insight, Jim. You helped (at least me) create the
Death of the Monolithic App (from here on in, DOMA), or maybe NanoApp. I
like that name, but naming is beside the point The importance of the
concept is the separation of tasks (which are generally mapped into a)
requiring human intervention, and b) not requiring human intervention.

As usual, I got sidetracked into the philosophy of design, when the
original question was, Given an app, how can I determine which of its
components are historical and currently unused parts? In SQL Server this is
not difficult, but I have no idea how to do this in Access.

Any ideas or suggestions or tools that can do this? Identify modules forms,
queries, etc. that are obsolete and can be deleted without harm, at least
as measured by their frequency of call?

-- 
Arthur