Normalize Lookup Tables??

[Navyguy]

So I have been getting back into this access stuff and poppa smurf has "forced me" to go back to basics as you can see from these two threads.

http://www.access-programmers.co.uk/...d.php?t=172219
http://www.access-programmers.co.uk/forums/showthread.php?t=172422

In my sample, the question is for this type of information "lookup tables", should they be normalized? It is clear that my "data tables" should be normalized…I have no problem with that and I understand how critical that is.

In my sample, I can see were possibly where there may need to be normalized as an example the name of a manufacturer changes or something, but that can also be done quite easily with an update query if needed. Price changes will always be done either manually (on individual items) or perhaps programmatically for wholesale changes…like all widgets increase 10%, which again could be done with an update query.

I have done a search both on the forum and on other sites…there does seem to be varying opinions….

Thoughts?

Cheers

 

[Guus2005]

I believe poppa smurf is stalking you

IMHO: Yes.

They need to be normalised. Wikipedia about normalisation.

If you don't it will be difficult to maintain your database.

All normalisation rules apply on each table. It doesn't matter what kind it is.
It will be a different story when your database is a datawarehouse.

HTH