If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
Cascading Combo Boxes -- Part 1
I need some help w/ cascading combo boxes in conjunction with subforms.
I posted a similar thread before, but I still haven't been able to get this to work. (Ken Snell was so kind to get me up to speed until this point and I'm not sure if I truly understood his additional recommendations in respect to using subforms). Before I post my question, I'd like to provide some detailed information about the tables, forms, subforms, etc. The description is quite lengthy, so please bare w/ me. I have a 3-tier One-To-Many table structure. - Division is "parent" of SectionCode - SectionCode is "parent" of BilletCode TABLE (and relationships): ************************** tblDivisions ============ DivisionID (Autonumber) Division (Text) tblSections =========== SectionID (Autonumber) DivisionIDfk (Number) SectionCode (Text) tblBilletCodes ============== BilletCodeID (Autonumber) SectionIDfk (Number) BilletCode (Text) FORMS AND SUBFORMS: ******************* First, 1. I have a mainform (frmBoards). This form contains general board information. Then, 2. tblDivisions is stored on frmDivisions 3. tblSections is stored on frmSections 4. tblBilletCodes is stored on frmBillets then A. frmDivisions has a subform (frmSections) B. frmSections has a subform (frmBillets) NOTE: all 3 forms (frmDivisions, frmSections, frmBillets) are displayed in "Datasheet" view DATA DEPENDENCIES FOR THE COMBO BOXES ************************************* At this time (for testing purposes), I have the 3 combo boxes for Division, SectionCode, and BilletCode on a single form. The cascading dependencies for Divisions, Sections, and Billetcodes are better understood with the following geographical example: Let's say: - Division = State - SectionCode = City - BilletCode = Community For instance, the values in the combo must are dynamic based on their parent value(s): - If State "CA" - then City "San Francisco" or "Los Angeles" - then Community "SF North", "SF South", "LA North", "LA South" - If State "FL" - then City "Miami" or "Jacksonville" - then Community "MIA North", "MIA South", "JVL North", "JVL South" etc.... the same principle applies for my 3-tier relationship betwen Division, SectionCodes, and BilletCodes THREAD WILL BE CONTINUED ON POST "CASCADING COMBO BOXES - PART 2" ================================================== =============== |
Thread Tools | |
Display Modes | |
|
|