Correct way to setup table/form

[Dorna Tucker]

I not sure how to setup the following fields in my table and also when I
create the form for the users to input the necessary information:

Employment (check all that apply):
___ABC Corp
___Singer Co.
___XYZ Management

The next field would read:
Marketing:
Start date
End date

The final field would read:
Other causes:
Yes (if user select yes, link to a field where exact information can be
typed)
No

 

[KARL DEWEY]

I am not sure if you set them up correctly but the way you stated them it
does not seem to be correct. A table does not have a statement like
"Employment (check all that apply):"

The next field would read:
Marketing:
Start date
End date

A field can not contain but one data element. Either the start or the end
date. You need two fields in the same record.

What are the other fields in the table? Name, address1, address2, city,
state, zip, phone, DOB, Sex, etc.

 

[Dorna Tucker]

Karl,

You are correct, the other fields will contain name, address, phone, email
address, etc. I wasn't sure how to do the fields I stated in this post. I
thought I could have a field named Employment and then list all of the
Employers so the users inputting the info in the DB would be able to select
all of the employers that pertain to that employee. The same would apply to
the Marketing field, I need to know the start date and end date.

I'm gathering from reading your message, I would need to have a separate
column/field for each employer. Am I correct with this assumption.

Also when I'm designing the form, can I have a label called Employment that
does not relate to any of the info in the DB and then list each employer in
the table in a vertical list under Employment. For example,
Employment:
ABC Corp
Singer Co
XYZ Management

Thank you for taking the time to reply to my post. I'm new with Access and
I get lost at time when designing the DB.

 

[KARL DEWEY]

Your use of terms do not match the common usage for a relational database and
Access.

I'm gathering from reading your message, I would need to have a separate
column/field for each employer. Am I correct with this assumption.

You need a separate record.
A relational database has a hierarchical structure like --
Person - all direct information that does not change DOB, Sex, Birth Place,
etc. This table will have a Primary Key (PeopleID), most folks use an
Autonumber, that is unique as a short identification method of the person in
ralating to other tables.

Their employement records will be in another table --
EmploymentID - Autonumber - PK
PeopleID - Integer - Koreign Key
Company - text -- You could have this as CompanyID and relate it to
another table - Companies
Position - text - Marketing would be a position held/performed.
StartDate - DateTime
EndDate - DateTime
Duties - memo
etc.

Just like grandparents - parent - child - relative (aunt, uncle, cousin,
brother, sister).