Database Structure

[radick_201]

First I want to apologize if this is posted some place else but was unable to find similar. I am putting together a database but unsure of how to structure it properly. I have a list of Municipalities and need to track all the Municipal Codes, Section Locations, Descriptions and apply a "Tag" for my reference use later on. My issue is that each municipality's code structure is unique to the other, for example Chapter 3 Subsection 5 references Fences for one municipality but for another may be found in Chapter 192 Subsection 8. I was already thinking I needed to have a Many to Many relationship somewhere but unsure. I've attached the relationship diagram of what I currently have. Any assistance would be appreciated.

[June7]

The chances that the same chapter number and description combination will occur in multiple municipalities appears to be minimal. Therefore, presuming each combination is unique to a municipality consider:

tbl_MunicipalityChapter
ID_MuniChap
Municipality
ChapterNumber
ChapterDescription
ChapterTag

tblChapterSubSection
MuniChap
SubSection
CodeDescription

Now the question is how long are the chapter descriptions? Do you have a standard set of descriptions? Should there be a lookup table of descriptions and save an ID into tbl_MunicipalityChapter instead of lengthy repetitive text?