Pallone:
I am going to try a different approach to the same idea: The objective is to establish a relationship between ModuleTbl and the CultureTbl, right? So let's do just that:
CultureTbl>--------<ModuleTbl
CultureID ModuleID This is a many-to-many relationship that says: "For each and every CultureID consists of 1 or more ModuleID". The reverse is also true, "For each and every ModuleID is made up of one or more CultureID". However, Many-to-Many relationships MUST BE resolved....hence the Junction Table, which is your ModuleStringTbl, which you created, sits between the CultureTbl and the ModuleTbl:
CultureTbl---------<ModuleStringTbl>--------ModuleTbl
CultureID ModuleID,CultureID ModuleID
What the above relationship states: "For each CultureID may consists of 1 or more ModuleIDs" and "For each ModuleID may consists of 1 or more CultureID"
In the above example there also exists relationships between the CultureTbl.CultureID and ModuleString.CultureID: "For each and every ModuleString.CultureID there exists 1 and only 1 CultureTbl.CultureID"; This relationship defines the CultureTble.CultureID as the LookupTbl as in a dropdownlist box. Also important is that as an administrator new CultureID's are added on the the CuluteTbl. The same is true for the ModuleTbl.ModuleID and the ModuleStringTbl.ModuleID.
Hope this helps.
========================
Disclaimer: The above comments are solely the opinion of one person and not to be construed as a directive or an incentive to commit fraudulent acts.
|