[AccessD] How to Handle Multiple People with the Same Name

[Dan Waters]

Hi Susan,

I have a table named tblProfiles.  This contains all the typical information
about every user.  There is a PersonName field, a PeopleID field.

Throughout the rest of the database only the PeopleID values are stored in
tables.  I need to do this because occasionally a person who is an active
user has a name changed, i.e., a woman changes her last name when she gets
married.  This allows the new name to be displayed throughout the
application while only making a data change in the tblProfiles table.

Trying to re-use a PersonName in a combobox would mean that the PersonName
would correspond to two different PeopleID values, and I would lose data
integrity.

Dan

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Susan Harkins
Sent: Tuesday, April 28, 2015 7:12 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] How to Handle Multiple People with the Same Name

Why?

Susan H.

On Tue, Apr 28, 2015 at 7:56 PM, Dan Waters <df.waters at outlook.com> wrote:

> Hi Susan,
>
> I need to keep the names from causing problems.  I can't use a 
> concatenation of other fields.
>
> Dan
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf 
> Of Susan Harkins
> Sent: Tuesday, April 28, 2015 5:35 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] How to Handle Multiple People with the Same 
> Name
>
> Depending on the number of records, even a middle name might not be
enough.
> You might want to include a birth date or even the ss# if you're 
> collecting those.
>
> Susan H.
>
> On Tue, Apr 28, 2015 at 6:15 PM, Jeff <jeff.developer at gmail.com> wrote:
>
> > I've always just tried to include a middle name after the first name.
> >
> > Sent from my iPhone
> >
> > > On Apr 28, 2015, at 4:54 PM, Dan Waters <df.waters at outlook.com> wrote:
> > >
> > > Suppose you are writing a system which sets up profiles for all users.
> > And
> > > you have two users whose names are both Dave Anderson (common in 
> > > Minnesota!).
> > >
> > >
> > >
> > > How have you handled this?
> > >
> > >
> > >
> > > Then, one Dave Anderson leaves the company, and later another Dave
> > Anderson
> > > is hired.
> > >
> > >
> > >
> > > Now what?
> > >
> > >
> > >
> > > If you've dealt with this or just observed a system that works 
> > > please respond.
> > >
> > >
> > >
> > > Thanks!
> > >
> > > Dan
> > >
> > > --
> > > 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