Rick Faircloth wrote: > > Positions (Yes, I like plural table names :o) > > Position_ID (Primary Key) > Position_Title > Position_Description > etc > > Employees > > Employee_ID (Primary Key) > Position_ID (Relational Key) > Employee_FirstName > Employee_LastName > etc
<or> > Employee_Positions > > Employee_ID > Position_ID > > > It seems like the third table is used to tie the Positions table and > Employees table together, > This may be a poor example of what I'm talking about. It is an excellent example. Just answer the following questions and it should all become clear :) How many positions can an employee have in your first example? How many positions can an employee have in your second example? How many positions can an employee have in your company? Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:202813 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
