Rick What you are referring to is a link table often used when you have a many to many relationship, if you have a one to one relationship then there is no need.
> > > It seems like the third table is used to tie the Positions table and > Employees table together, but I don't see the benefit of creating that > third table when I can just put the Position_ID in the Employees > Table... > If one employee can only have one position at one time then there is no benefit, however if an employee has many positions or many roles then employee positions would allow you to retrieve all the positions for a particular employee without having a repeating group or redundant data in your employee table (i.e. multiple rows for the same employee but with different positions.) HTH K ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:202814 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
