RichardRay
Registered: 07/01/09
Posts: 80
|
| | 11/04/09 at 02:53 PM | Reply with quote | #1 |
|
I've looked at both the videos demonstrating drop down lists with the choices in List 1 controlling the choices in List 2, etc. One (for version < 6) uses a data design in which the parent and child choices are combined in a single table. The second one (for version >= 6, Code Customization Wizard) requires that both the parent and child choices be included in the record for which only one is dependent. In my case I only need the value from the second list, so storing the FK to the table that generates the first one seems unnecessary and a bit kludgy. i.e. -
Table1 has an FK to Table3. Table2 has an FK to Table3 that helps segregate the Table3 values for easier comprehension. On the layout for Table1 I want to display Table2's values and then restrict the Table3 choices based on what's related to the Table2 choice that's been made.
Is there a way to do that in ISD that doesn't require a great deal of code rolling? Or, shall I just get down of my normalized high horse and store both FK's?
__________________
Richard Ray
Jackson Hole Mountain Resort
Teton Village, WY |
| Loading... | |
RichardRay
Registered: 07/01/09
Posts: 80
|
| | 11/04/09 at 04:54 PM | Reply with quote | #2 |
|
OTOH, maybe I can do this with a view? Keep the db the way it is and define a view with both columns in it? Seems like something like that might work - I'll see how that works...
Other suggestions still appreciated.
__________________
Richard Ray
Jackson Hole Mountain Resort
Teton Village, WY |
| Loading... | |
RSS(.NETCodeGenerationIsHere).gif)
