Many to many relationship?

Question

Guys I am trying to make a simple ticket generation system for my company as a favor. For now, I have a table called tblTicket and another table called tblEng

Answer 1

I would suggest making 1-to-Many relationships instead of making many-to-many relationships. You can accomplish this by having a table that maps between your tblTicket and tblEngineer. For Example:

tblEngineer
-----------
(PK) iEngineerID


tblTicket
---------
(PK) iTicketID


tblTicketEngineerMap
--------------------
(PK) iMapID
(FK) iEngineerID
(FK) iTicketID

By doing it this way, an Engineer and a Ticker can be in many maps, making two 1-to-Many relationships, and allowing the functionality you seek.

Check out this thread as to why you should try to avoid many-to-many table designs.