[AccessD] Another normalization question

Darn, and I was looking forward to seeing them outfitted with something
like the headbands they put on babies now so you can tell what gender they
are!  LOL

Charlotte

On Wed, Sep 17, 2014 at 2:49 PM, Susan Harkins <ssharkins at gmail.com> wrote:

> At this point, it isn't important. We have two people that do this and
> they'll know when someone's gone and who to call instead. It isn't a
> priority, not now anyway. It is something we can add later if she wants.
>
> This morning, we worked out a scheme for iding the box turtles -- we're
> going to use nail polish on their bellies and id them as M1, M2, F1, ...
> and
> so on, where m is male and f is female.
>
> We're nothing if not creative. :)
>
> Susan H.
>
>
> If you have a telephone number table, a contact who leaves can easily leave
> his office number to his replacement, right? And the same contact who has
> multiple phones, including 3 mobile numbers can be accommodated without
> widening the contact table.
> On Sep 16, 2014 6:48 PM, "Susan Harkins" <ssharkins at gmail.com> wrote:
>
> > You bring up a point I hadn't considered -- inactive folks. Thank you!
> >
> > Susan H.
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bodin
> > Sent: Tuesday, September 16, 2014 3:49 PM
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Another normalization question
> >
> > Create a one--many linked Contacts table.  You can add a date field
> > for "Inactive Date" on the Contact record to go along with name,
> > department, phone number, email address, whatever.  If it Inactive
> > Date gets filled in, you will know the contact is inactive as well as
> > when the contact went inactive.  You can then filter on this field to
> > only show/report on active contacts.  Then you will not lose any
> potentially important numbers.
> >
> >
> >
> >
> >
> > John Bodin
> >
> > jbodin at sbor.com
> >
> >
> >
> > ________________________________________
> > From: accessd-bounces at databaseadvisors.com
> > <accessd-bounces at databaseadvisors.com> on behalf of Susan Harkins
> > <ssharkins at gmail.com>
> > Sent: Tuesday, September 16, 2014 3:13 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
> >
> > --
> > 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
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>