[AccessD] Another normalization question

Susan,

Re my post of possibilities - mostly so you can include appropriate bits in the
'contact details' table.
I would definitely recommend including a comments field (up to) 250 chars of
text can be very useful.

And if the office cat has a web id - as in locator is it an employee or a
person.
Ditto the organisation directors.

JimB


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Wednesday, September 17, 2014 1:46 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Another normalization question

"Gotta love the distinction between persons and employees"

Heh... I usually just have a "Humans" table and attach whatever criteria(s) are
necessary from there.

Cheers
Darryl

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bill Benson
Sent: Wednesday, 17 September 2014 10:23 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Another normalization question

I just checked the adventureworks2012 sql server sample database and yes, there
is a personphone table with fks to the businessentity table and the
phonenumbertype table as I had suspected. Not pushing the idea further, just
confirming that I have now been able to go back and do my diligence.
However, there is no businessentitytype table as I had mistakenly assumed there
to be. So apparently there is no attempt to distinguish what type of an entity
is getting associated with a given phone number ---- e.g., institution, person,
Bessie the cow... :-). It seems that the BusinessEntity table is just a log of
all the, uh, entities that have been registered within the database, which
includes in the case of that database,
	Employees
	Job candidates
	Businessentitycontacts
	Persons
Gotta love the distinction between persons and employees, but I did not see a
table called corporations so I guess what Romney said was really true,
corporations are people too (unlike employees I guess)  :-Q

Stuart, I owe you an apology (whether or not you are still reading). I guess
this businessentityid thing is just so that all those classified entities don't
need their specialized keys (and corresponding FKs in the fact and junction
tables, the businessentityid suffices.


I don't really half know why this database is set up the way it is, I have not
read any documentation on it yet.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Tuesday, September 16, 2014 6:45 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Another normalization question

Bill, this sounds similar to what Mark suggested. It sounds like the way to go
for me. 

Susan H. 


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

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