Re: searching for names - multiple names per record

Tech-Archive recommends: Fix windows errors by optimizing your registry

No, I don't think you should have a separate table for each name type. Have
a single name table with an additional column of NameType.

That'll make queries like "Let me know all records that John Brown is
involved with", "Let me know those records for which Mary Smith was the
Approver" and "Let me know all records where the same person was the
Developer and the Originator" much, much simpler.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"zSplash" <zNOSPAMSplash@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23bVu3alRHHA.4188@xxxxxxxxxxxxxxxxxxxxxxx
Thanks, Doug, for responding.
By "create a second table linked to that first table with one row for each
name" that I should have individual tables for each nameType? That is
leave the mainTable with the common information, and then create a table
for nameOriginator, a table for nameApprover, a table nameDeveloper, etc,
with nameData for each of those nameTypes?

"Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxxx> wrote in message
news:up0Yg8kRHHA.3948@xxxxxxxxxxxxxxxxxxxxxxx
You'd better explain your precise need, but in general, you wouldn't put
multiple names on a single record.

Typically when you have multiple names on a single record, it means
you've got field names like "Originator", "Approver", "Developer" etc.
That's not a good idea: you're hiding data in the field names.

Instead, you should keep the common information in the one table, and
create a second table linked to that first table with one row for each
name.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"zSplash" <zNOSPAMSplash@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:O9hw1zkRHHA.4744@xxxxxxxxxxxxxxxxxxxxxxx
My database needs to track several names (first and last) for each
record. My initial database had all the names (first/last) in the main
table. In an earlier request for help re: searching for lastnames,
someone suggested that I put all the names in a separate Names table
with a nameType comboBox. Now that I've modified my database to do
that, I see that with that design I can only have one name per record.
(To enter names, I select nameType, and then enter first/last names for
that nameType. I have no way of entering/adding the first/lastnames for
the other nameTypes. Each record has 5 or 6 first/last names to track.
If they are all in one Names table, as suggested, I can only hold one
nameType in each record.

Can someone please suggest another way to solve my problem?

TIA








.

Relevant Pages

  • Re: searching for names - multiple names per record
    ... Typically when you have multiple names on a single record, ... My initial database had all the names (first/last) in the main table. ... select nameType, and then enter first/last names for that nameType. ...
    (microsoft.public.access.gettingstarted)
  • Re: searching for names - multiple names per record
    ... Project C John Brown John Brown Mary Smith ... with the combination of Id and NameType as the Primary Key. ... My initial database had all the names (first/last) in the main ...
    (microsoft.public.access.gettingstarted)
  • Re: searching for names - multiple names per record
    ... Thanks, Doug, but I just don't get it. ... Have a single name table with an additional column of NameType. ... My initial database had all the names (first/last) in the main ...
    (microsoft.public.access.gettingstarted)
  • searching for names - multiple names per record
    ... My database needs to track several names for each record. ... My initial database had all the names (first/last) in the main table. ... I put all the names in a separate Names table with a nameType comboBox. ...
    (microsoft.public.access.gettingstarted)
  • Re: searching for names - multiple names per record
    ... name" that I should have individual tables for each nameType? ... Typically when you have multiple names on a single record, ... My initial database had all the names (first/last) in the main ... Now that I've modified my database to do that, ...
    (microsoft.public.access.gettingstarted)