Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Why set relationships? Vs fill-in using a Form?

Status
Not open for further replies.

Ackcess

Technical User
Nov 24, 2004
1
CA
Hi!

Say I have a t_Employees and I have a table t_Employment type which lists 4 options to choose from: full-time, part-time, casual, on call. For each employee, I will select/input their Employment Type.

What is the difference between:

a) creating a table t_EmploymentType and no relationship link to table t_Employees, then just using a form with a lookup to fill in the information

versus…

b) creating table t_EmploymentType with a primary ID key, creating a relationship to t_Employees, then either filling in via table, form, or query using a lookup combo box?

Is one method better than the other? If I don’t create a relationship, do I lose out on some query/reporting functions?

If I should be creating relationships for this “fill-in” tables, do I need referential integrity?

Thanks for any enlightenment,

Derek
 
I never create relationships to lookup tables.
I just don't let users delete from lookup lists.

Some other developers take a different view from me.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top