Sooooo.Create a lookup that contains first and last name, but store say the
SS# of the parent rather than the name. I had succeeded in doing that much,
but to make it user friendly for the group of females I am writing this
database forname would of been better in that regard.Thanks
You're missing my point.
The user SHOULD NOT see the table. It makes no difference to the user whether
the table contains a name, a social security number, a meaningless Autonumber,
or even an unreadable GUID.
The user will instead be interacting with a Form. That Form can use tools such
as Subforms and Combo Boxes to *DISPLAY* human meaningful information, such as
names, while it *STORES* the unique ID.
First and last names are *NOT* reliable keys in any case; I know three
gentlemen named Fred Brown, right here in the little town of Parma. You *do*
need a unique ID of some sort.
John W. Vinson [MVP]