Reply to thread

Message: [QUOTE="BruceM, post: 2567329"] An employee may be in many groups, and a group may have many employees. That is a many-to-many relationship, which you need to resolve through a third table, often called a junction table. It contains its own primary key, plus an EmployeeID field and a GroupID field to correspond to the primary key fields from the Employee and Group tables. There is a one-to-many relationship between each of the PK fields and the corresponding fields in the junction table. You would typically have a main form based on either the Employee table or the Group table, and a continuous subform based on the junction table. If you have based the main form on the Group table, the juction table would typically contain a combo box that gets its row source from the Employees table. It would be bound to the EmployeeID field. Basing the main form on Group will let you fill in the group roster. Basing it on Employee will let you view all of an employees group assignments. You could have both, depending on your needs. Same for reports. You mentioned JobID, but made no mention of how this fits into the picture. [/QUOTE]