[AccessD] Mucking around

Terminology happens :o) 

Conceptually I think the easiest way to understand it is using the
Query/Report analogy.

You create a Query which makes it possible/easier/more efficient to create a
specific Report. Its a means to produce a product.

Remember, rarely does any lay person care about HOW data is stored, they
generally only care about how it is presented (product). Its up to the DBA
to store it correctly so that it can be presented in any one of the myriad
of ways it can be used/presented in the future. The granularity of a
properly normalized data structure allows for the most flexibility in this
regards.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
max.wanadoo at gmail.com

The terminology is throwing me a bit too (well, to be honest, it is throwing
me a lot).
With the help of you guys, I will undertand it eventually.

What is conceptually throwing me at the moment though is this:  If the
reason people use datamarts (Star/Snow) to quickly create reports which
dice/slice down through the data, then are we or are we not just moving the
"time Taken" from the report stage to the data input stage (which would make
sense to me).  But if I am completely wrong here, then I really am "all at
sea!"