[AccessD] Mucking around

Hi John,

>Terminology happens :o) 

Yes, but sometime what is really simple becomes difficult to understand
because the terminogy is not understood.
I can remember when I was at school (albeit a long time ago, but I have a
good memory), I had great difficulty understanding English Grammar.  I just
couldn't understand what the teacher was saying Verbs, Adverbs, Adjectives,
past participle, etc.  This lasted for many years until, in the Army, I was
posted to Germany and had to learn German.  Then I picked it up in a flash
and became quite good in a short time, reading, writing and (accent
excepted), speaking German. Much of it gone now, sadly.

What I realised was that when I was learning German the teacher was using
English to explain German grammar and I was able to differentiate between
the German word and what the explanation of what the word meant when spoken
in English.  

I then realised that the reason I couldn't understand English Grammar at
school was because the teacher was using English words to explain English
words and I couldn't differentiate  between the word and the explanations
all mixed in with his general speech, whereas when I was learning German,
the difference was obvious. 
I actually learnt English Grammar by learning to speak German!  All because
of terminology.  

I learnt that "To boldly go where no man has gone before" is a split
infinite and I (now) know why.

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
Sent: Friday, September 28, 2007 8:04 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [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!"


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com