I would use a conditional value list. Make a single field the source of values for your value list, but with one set of records you "Finnish" values and another set of records your "Senagalese" values. Another field in the record can label them by language type. If this is a case where you are using two fields, the first to enter an ID code and the second your "language specific text", add a third field for that value. (There will be groups of records with the same ID value, each for a different language.)
For how to set up conditional value lists, you can start with the "basic conditional value list setup" found in "Adventures in FileMaking #1 - Conditional Value Lists".
Nope... that doesn't do it.
- I can't understand why it's not possible to set ValueList's with a calculation?!?!?!
That would make ALOT of things easier!
(Maybe my v.10 is just too old?)
As I see it, it's not possible, since I can't "override" a set ValueList.
The version you suggested, is AWFULLY awkward! Why would I like to do this???
I will continue, by time, to think of possibilities...
(I was actually thinking of a normal text field that just suggests a value (from a lookup) as I type .
(is THAT possible??) lol.
Thanks for your suggestion again.
Why can't that do it? It's helpful to those helping you if you explain why "That doesn't do it".