1 of 1 people found this helpful
Your screen shot does not show any relationships linking the table occurrences. Most conditional value lists require a relationship. Some do not. In the Adventures file, You have several different conditional value lists, some of which use ExecuteSQL and thus do not need relationships and others do not use ExecuteSQL and thus do need relationships. The relationships needed for any given example are clearly documented on the layout where the example is located.
So which specific hierarchical conditional value list example are you trying to implement?
Please note that the relationship basis typical of most CVL's can be a significantly limiting factor as it can result in not only creating more table occurrences and relationships in your solution, but also more copies of the same CVL in manage Value lists where the only difference are the table occurrence references used.
You might also look at the script produced conditional value list and the selection portals used in the Adventures in FileMaking #2 file (there's a download link in additional resources layout). The selection portals might be used with a selector connector design (see the Geist Interactive web site for articles on this enhanced version of Anchor Buoy), to get a single selection control that can be copy/pasted from one layout ot another when building your solution.
Another option might be to web search "virtual list" to see if that method works for you.
Sorry for the late respons.
I am I aware of the missing relationship.
I am trying to copy your Hierarchical Conditional Value Lists II -- although I am not sure if it is the correct one to adapt/copy.
I really want the Value List to be as adaptable as possible, meaning I would like the Value List to be used in every instance of my database, regardless of where the clients are positioned in the database.
My thoughts are.
First, I select a desired Customer.
Second, I select a desired Department -- only showing the departments under the desired Customer.
Third, I select a desired User -- only showing the Users under the desired Customer/Department.
As mentioned, I really want the Value List to be as adaptable as possible.
Could you parse me in the right direction?
And please feel free to ask questions, come with inputs or yell if info is missing.
You've indicated what you want and what you are attempting, but how exactly is it failing for you?
And have you been able to set up the needed relationships?
Can you post a screen shot of them?