[AccessD] normalization question

To add to this point.....

A table with names will not guarantee that a name is correct or unique;
therefore a table with only that information can not be normalized. The only
way that I have found it is possible, is if the full name with DOB as a
minimum requirement and maybe SIN as added insurance. Even though a single
SIN number should guarantee uniqueness, you are of course dealing with human
data entry issues.

My two cents worth.
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Martin Reid
Sent: Sunday, May 16, 2004 1:51 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] normalization question


Why would you have a table with only names?

In my experience there is usually another qualifier? But I am sure someone
here will come up with an interesting approach to this one.

Martin



----- Original Message -----
From: "Susan Harkins" <ssharkins at bellsouth.net>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Sunday, May 16, 2004 9:42 PM
Subject: [AccessD] normalization question


> If a table contains only names -- say first and last -- and you relate
those
> records to other tables -- how to you deal with real people with the same
> name? I feel like I'm stepping off a cliff here...
>
> 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