Tables

[Guest]

I need to create a database that holds information about Sites and the
Personnel and these sites. Usually the site info (address etc) is the same
for all personnel. However, sometimes the personnel are at a different
address. Should I create a table for sites and have address, city state etc.
and create a table for personnel with the same info (address,city state
etc.) Each personnel would have different phone numbers fax, email. Would I
create a table called sites and have all the information in it and then
another table called personnel and have the same info and relate them by both
having site number in the table. I havn't used Access for years and I am just
trying to get back into it. Any help would be appreciated.

Best regards
Dee

 

[Nikos Yannacopoulos]

Dee,

If I understand corretly what you are saying, then you need three
tables: tblSites, tblPersonnel and tblAddresses.
The idea is that all addresses (site addresses plus off-site personnel
addresses) are recorded in tblAddresses, with an AddressID field plus
all other like ciy, street, state, zip etc.; tblSite does not have
address details in it, instead it has an address number field, joined to
the AddressID field in tblAddress; the same goes for tblPersonnel. For
each new personnel, you can default in the site address number as soon
as a site is selected, and change it only if the particular personnel is
based off-site.

HTH,
Nikos

 

[Guest]

Dear Nikos,

Thank you for your help. I am not sure the part about default in the site
address number as soon as a site is selected, and change it only if the
particular personnel is based off-site. Since there will be very few
personnel who will actually have a different address than the site could I
create a table called Off-site Personnel and have the addresses there and
link to the site table by the site number.

Thanks again for your help.

Best regards,

Dee

 

[Pat Hartman\(MVP\)]

You need to insert a level into your hierarchy. If you want to maintain the
current terminology, you can use a site table and an address table. The
address table is related to a site. So each site can have 1 or more
addresses. People should be related to address rather than to site. That
allows each person to have a separate address but still allow them to be
grouped by what you are calling "site".

 

[Nikos Yannacopoulos]

Dee,

Not sure I understand what you mean, but sounds like you're asking for
trouble... Your data design must be consistent (and, needless to say,
normalized!); allowing some "exceptions" will make your development very
hard further down the line.

Nikos