[AccessD] Another normalization question

Susan Harkins ssharkins at gmail.com
Tue Sep 16 17:45:13 CDT 2014


Well, at the risk of making you all groan... I don't think it'll ever be
that complicated, but this is a great breakdown. Thanks!

Susan H. 

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

Separate table with FK back to the institute and 'contact name' and 'contact
title'

Multiple entries allowing multiple numbers per person, and multiple people
per number and person associated with multiple organisations 

Maybe an additional keys giving a priority on number for person, and
priority for organisation Also times/dates/days  that numbers apply, or do
not apply

You can have a person working at multiple organisations doing different
types of tasks at different times Manager at one place, volunteer at another

Basically - a searchable text field - or maybe 2 so the contact times can be
separate from other notes.
Setup a standard  set of prefixes for the search to indicate Available
weekDay MTWTFSU Periods from-to yyyymmdd-yyyymmdd
  
Also  email contacts #codes facebook website - so many ways to contact
people now-days, but you basically need to know who - for what  where and
then the rest will be ok as text with pre-assigned prefix codes to let the
reader know how to use the 'value'.

And some of my clients have contact email and answerphone landline.
Others have my cell number - not answered when I'm actually working with a
client.
Others get the personal number - is answered even if I'm working, or it's
later than 7pm And I only have 1 'employment' at the moment.

I used to be 'distribution manager' for several apps, systems support & DBM
for mainframe, PC and network support and maintenance team leader as well as
doing onsite liaison.
That was real 'fun' especially when I found out the mainframe ops had the
phone numbers of my local alehouses - not even safe of a Friday evening! 

JimB


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

I'm still working on the animal tracking database. It's going Okay, but I
don't have a lot of free time to work on it. ;)

Right now I'm hashing through institution contacts and phone numbers. I
think, for the most part, that most phone numbers will belong to the
institution, but maybe not -- what if the institution has more than one
contact and each has a number? On the other hand, if I relate the phone
number to the contact and the contact leaves, I lose the phone number, which
might rightly belong to the institution.

You know, looking back... I can't remember how I handled this in the past.

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



More information about the AccessD mailing list