[AccessD] Normalization discussion

 I think you've got what your saying is the parent and child tables mixed
up, which is why it's confusing.

 A FK always goes in the child table.

  So if I have tblBreeds and tblAnimals, Breeds is the parent table and the
PK from that would go in tblAnimals as a FK so you'd know what specific
breed a particular animal was.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Friday, August 29, 2014 09:07 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Normalization discussion

I'll spend the morning rereading the book Martin and I wrote, brushing up
on the normalization part. I've forgotten a lot of the basics. I'm writing
an animal tracing database in Access and I'm trying to remember if it
matters where the fk goes. Now, I remember its purpose and all that, but it
would be so much simpler if I could just drop them all into the main table
instead of adding a fk to all the child tables to the main table -- I think
anyway.

So, I've got a main table of animals and all of the remaining tables are
child tables of a sort and a few lookup tables. Is it reasonable to just
add a fk to all those child tables in my parent table?

I just don't remember. I haven't built a database in... seriously... 10
years? It's been long enough that I'm really struggling.

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