Filtering, as in filtered portals, only works in portals.
Filtering via a relationship requires defining a relationship. You can use a global field on the parent-side to filter the results from the Child-side (value list table). As far as I know, only actual field values can be used to filter relationships, and only relationships can filter value lists based on data.
This is how I would try to do what you want:
1. Add a global text field Language to your table.
2. Create a new table with the following fields: Value (number), Language (text), YesNo (text), AccountType (text), Gender (text), etc. One field for each type of value list.
3. Populate the new table, i.e., First Record would be 1, English, Yes, Balance, Male etc.
4. Create a relationship from your table to the value list table where gLanguage = Language.
5. Create Value Lists, one for each type using the field from the value list table based on the relationship create in 4.
You may also want to create a value list of languages.
Nicely explained! I was able to implement a robust filtered list from your helpful response. Thanks.
Thanks. I managed to get it working.
Be so kind to explain what you meen by a global text field. Is that a field with the same value for each record?
1 of 1 people found this helpful
A global field is not part of a record, it is part of a table. It is stored differently than other fields. Thus it has the same value for each record.
In my ignorance I profided the gLanguage field an auto enter option.
I thicked the "data" box en entered a value "NL".
The global field solution is more elegant. A change in one of the records is carried through all the records