Define "report"...
How complex? A simple report against a single table? A multi-table source
with multiple related sub-reports? By someone who designed/developed the
table structure, or by someone who's never seen the tables and doesn't
understand relational data?
As a rough rule of thumb, first create a query and make sure it returns the
data the report will need. Then base the report on the query.
This handles the "joins across multiple tables" situation.
Unless you already have a pre-existing report defined that you can use as a
starting point/template for a new report, it might be faster to use the
report wizard to generate the "bones" of a new report. Then customize it.
With all the stars aligned and a knowledgeable programmer and a template and
a user willing to look at a "first draft" version, figure an hour.
Fine-tuning it after that could take ... ?!
Regards
Jeff Boyce
Microsoft Office/Access MVP
