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

[Darryl Collins]

Maybe I misunderstand the issue here, but wouldn't you have a master table of user names all keyed individually and unique.  As part of the master table you would include link to a table showing start date and an end date (or active / inactive if you prefer in the main table, although the date option in a 2nd table is more powerful and useful) along with other unique ID data in the master profile table (usually DOB for example).

So keyID 1 "Dave Anderson" is not and cannot ever be KeyID 5 "Dave Anderson".

Or am I missing something here?

Cheers
Darryl.



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Wednesday, 29 April 2015 7:54 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] How to Handle Multiple People with the Same Name

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