to understand table/queries/form/report before setting up table structure?

[Harrold]

Hi

Is it required to understand table/query/form/report before building a database?

The reason i asked is because when i post question on the forum about my design, you guys tend to tell me to do it at form/queries, etc. Hence, i would like to clarify the matter. I dont want belatedly my design fail here and there.

Thanks in advance

 

[pbaldy]

In my opinion the first order of business is designing the tables using proper normalization rules. Perhaps what you heard was that users should only see forms and reports, which I agree with.

 

[John Big Booty]

A normalised table structure, is the foundations on which any good DB is built.

Forms allow your user to interact with the underlying data in a meaningful manner, whilst Reports allow your user to produce a hard copy representation of that data.

Whilst Queries gather the data together in a manner that can then be displayed within your Forms and Reports, that is not to say that a Form or Report can't be based directly upon a table, but in most cases a Query or number of Queries will be required to bring the data together for display purposes.

 

[John Big Booty]

Your turn to beat me to the punch this time Paul