Technologies: ASP.NET MVC 3 and Entity Framework 4.3+
I have two domain models Complaint and Employee. 1 Complaint can have 1 or more Employees. The Employees table is a living repository of Employee information. Am thinking that I would need a third table to track each employee that has a relationship to 1 Complaint/multiple complaints??? If so, how would I move forward with creating this "Repository/Tracking Employees per Complaint" table?? Do I need to create another class? I would like a form to appear where I can select multiple employees from a Listbox, and save data back to the database. If I call or looking for a particular Complaint, I would like to see all related employees to unique complaint.
Properties for Complaint Domain Class:
public int id {get; set;}
public string ComplaintReason {get; set;}
public DateTime ComplaintDate {get; set;}
public string EmployeeName {get; set;} (I think I should convert this to ICollection<Employee> or Third Class Repository??)
Properties for Employee Domain Class:
public int id {get; set;}
public string FullName{get; set;}
The complaint form needs to have a field Listbox called Employees, users can select Multiple Employees and save the form. When a complaint record is queried, it should return all employees associated with the complaint record.
Hi, I am a windows/web apps developer/designer with experience in ASP.NET/PHP/HTML/CSS/JS/PS &C# & MSSQL/MySQL DB. Contact me if interested. Thank you, ValyB