No Duplicate Names

I am seeking to create a table of names in a manor that will ensure there are
no duplicate names from a particular address. For instance it would allow for
separate records for John Smith at 123 Main Street and John Smith at 456
Broadway, but not two records for John Smith from the same address. I've
tried creating a primary key using fnme, lnme, and add, this does ensure the
unique records but does not allow enforcement of referential integrity.
P.S. Can someone suggest a good book that might be able to turn a relative
simpleton of databases into a well versed access user. Thank you all in
advance for your advice.

Jimmi

Are you concerned with the possibility that John Smith has a son named John,
living at the same address?

Good luck

Jeff Boyce
Access MVP

"Jimmi B" wrote in message
...
I am seeking to create a table of names in a manor that will ensure there
are
no duplicate names from a particular address. For instance it would allow
for
separate records for John Smith at 123 Main Street and John Smith at 456
Broadway, but not two records for John Smith from the same address. I've
tried creating a primary key using fnme, lnme, and add, this does ensure
the
unique records but does not allow enforcement of referential integrity.
P.S. Can someone suggest a good book that might be able to turn a relative
simpleton of databases into a well versed access user. Thank you all in
advance for your advice.

you might try using an Autonumber as the primary key in your table, and
simply creating a unique index using the fname, lname, add fields. that will
ensure "unique-ness", will at the same time providing you with a
single-field primary key to use as a foreign key in related tables.

suggest you give some thought to Jeff Boyce's question, or you may find
yourself with data that you're unable to enter into your table, at some
point.

as for books, depends on your current skill level. for newbies, i often
recommend the "Microsoft Access version Bible" by Prague and Irwin.
"Building Microsoft Access Applications" by John Viescas has been often
recommended by expert developers here in the newsgroups. i haven't seen the
book myself but i trust the judgment of those who have, so i'm confident
it's a valuable tool - i'm just not sure what skill level it's aimed at.

hth


"Jimmi B" wrote in message
...
I am seeking to create a table of names in a manor that will ensure there
are
no duplicate names from a particular address. For instance it would allow
for
separate records for John Smith at 123 Main Street and John Smith at 456
Broadway, but not two records for John Smith from the same address. I've
tried creating a primary key using fnme, lnme, and add, this does ensure
the
unique records but does not allow enforcement of referential integrity.
P.S. Can someone suggest a good book that might be able to turn a relative
simpleton of databases into a well versed access user. Thank you all in
advance for your advice.

"tina" wrote:

you might try using an Autonumber as the primary key in your table, and
simply creating a unique index using the fname, lname, add fields. that will
ensure "unique-ness", will at the same time providing you with a
single-field primary key to use as a foreign key in related tables.

suggest you give some thought to Jeff Boyce's question, or you may find
yourself with data that you're unable to enter into your table, at some
point.

as for books, depends on your current skill level. for newbies, i often
recommend the "Microsoft Access version Bible" by Prague and Irwin.
"Building Microsoft Access Applications" by John Viescas has been often
recommended by expert developers here in the newsgroups. i haven't seen the
book myself but i trust the judgment of those who have, so i'm confident
it's a valuable tool - i'm just not sure what skill level it's aimed at.

hth


"Jimmi B" wrote in message
...
I am seeking to create a table of names in a manor that will ensure there
are
no duplicate names from a particular address. For instance it would allow
for
separate records for John Smith at 123 Main Street and John Smith at 456
Broadway, but not two records for John Smith from the same address. I've
tried creating a primary key using fnme, lnme, and add, this does ensure
the
unique records but does not allow enforcement of referential integrity.
P.S. Can someone suggest a good book that might be able to turn a relative
simpleton of databases into a well versed access user. Thank you all in
advance for your advice.


Thank you for the replies. To answer Jeff's question; no, what I am trying to develop is a complaint tracking system wherein a user could track complaints by complainant. My fear is that if some individuals call frequent ly they would create needless records in that table and secondly if an individual moves I would like to keep the referential integrity. Perhaps my logic is flawed in thinking that I need to assure that records are unique. Thank you for the titles, I will try the Access Bible.