No way to do that. Table based value lists are very easy to maintain and work with, so I don't really see the need for this.
What reasons do you have for not basing your list of values on a table?
Wow, thanks Phil for your fast answer.:-)
Well,"my" reason is ease of use for the client. Having a custom value list, the client can edit it "on-the-go", if he is missing a value. He doesn't have to go to the related table and make a new record, but instead clicks on "edit" and just adds a value to the value list.
I thought maybe a CASE calculation could do the trick, since the values of the selection field are limited.
So for example Case ( table::selection = print ; ValueListItems ( "file" ; valuelistA ) ; ... ) .
Something like that, if you understand what I mean (I'm far from a pro :-))
Table based value lists can also be edited "on the go".
You add an "edit" button next to the value list field that takes him to a layout where the table of values are displayed. You can even use New Window to pop the list up in a small floating window. Unlike custom value lists, you can enable spell checking, sorting, formatting, auto-enter calculations and validation rules to make editing the value list more user friendly than a custom value list. Those options wouldn't be needed for a short list, but as your list of values grows, such features can make managing the list from a table much easier than a custom list.
There is one case where a custom value list still has an advantage over table based lists: You can specify an order for the values that is not sorted in ascending order. There is a trick for forcing a different order for table based value lists, but you lose the use of the second value column and it works best only for fairly short lists of values.
That sounds just like what I need, and you are right, this offers more usability than my idea.