Good morning. I think that it is not the appropriate design, you must have a table specks and a code_violations table, if you need to associate in a many-to-many relationship you must have a third table in the middle where you can create several notes to several code_violations.
Ok, that sounds fine but just to be clear the Note is the parent record and I am trying to add multiple Code Violations tothe Note record. How would I set that up right now I have it setup as the Parent Table is HazMat_Codes and child is Notes and "Code-Violation" field is a lookup field in Notes table.
I'm not sure about your question, but the correct desgin is:
Hmmm sorry for not understanding. I struggle with the whole table lookup setup. This is the dropdown and how it is currently being displayed on the form so it is showing the information I want. I just want the option of adding another code violation to the form if I want.
You would just have to create another field and create a new relationship, but I insist that this is not correct from a design point of view, you would have a redundant relationship and the limitation of only two fields, and if you need 3 or 4 or 5? are you going to create 5 fields and 5 relationships? It is best to have the "intermediate" table
