What would you like to do exactly ?
What do you mean exactly?
2 of 2 people found this helpful
FileMaker's value lists are very limited in comparison to similar products.
You can complain about it in FeedBack
You can look for a product idea asking for what you want and vote for it if you find one or create one if you don't.
You can consider it a challenge to be overcome.
I will note that some of the examples in #1 use SQL to produce the value list--not exactly "based" on SQL, but it works.
2 of 2 people found this helpful
FM native value lists are really not up to date. There must be feature requests
One solution is the 'Magic Value List' method by Bruce Robertson. There are a few tricks to bear in mind - but basically one can set up a sql query (more general: A list) and use the results as a value list. On the fly!
the last trick: We need a relationship for that MaVaL -> use a separate table for that, otherwise the MaVaL won't work in find mode...
Kevin Frank wrote examples for MaVaL, I have a blog entry about MaVaL, unfortunately in German. There are many search results when google for it
尚升 郭 wrote:
Is FileMaker still a database?
More correctly, it is a toolbox for building databases.
Being able to create a value list from a SQL Statement seems like such an obvious thing to have in 2017 it's amazing people say that we need to "suggest it" to FMI. (Like v. 1.0 type functionality: search & replace in scripts that still isn't there.)
To me, that's like "suggesting" to a car dealer that a car have .... air conditioning. Cars didn't use to have air conditioning standard, but try to find one now that doesn't.
Hello? This is 2017. SQL is everywhere. Tech Support wrote me to say "FMP isn't a SQL database" Huh?
In any case, I stopped using SQL in FMP since it constantly hung my machine and isn't supported where I wish it were (like value lists) and still, after five versions, only supports a limited "SELECT".
others defined that like this: FileMaker is the basic extension fir the MBS Plugin
1 of 1 people found this helpful
Well, yes and no. A value list is:
- custom values entered into a dialog
- values from a field, based optionally on a related context
"from a field" is powerful if you consider you can have:
- one "value" (word or phrase) in one field with many records
- many "values" (return delimited) in one field in one record
I use the 2nd "list" many times and if you can Set this single field with the result of an ExecuteSQL(), then use it.
I was thinking back to Visual FoxPro. There you could do most UI list populations with a SQL statement.
VFP being the interface, of course. Not all SQL dbs have all Lists, Arrays, Collections, Structures, etc. type of columns. And AFAIK, no SQL db has "multi-line keys" (relationships based on return-delimited lists), like FM.
We do what we must do...
just create a 1 record table, sql yourself silly in a field and use that field to build a value list.
In your other file, define a value list based upon either
Use values from a field (the above field)
Use value list from another file (we have a file called ValueList which catches'em all)
I wasn't finding fault with FMP, just wishing yet another basic feature was there.
Ditto. We do what we must (wherever we must)!
Sent from miPhone
For years, I have pointed out that the basic combo box that you can find in MS Access runs rings around FileMaker value lists.
- You can use an SQL query as the data source
- You can use any number of columns (fields) that you want
- You can sort the values any way you want on any column that you want, even on a column not visible in the value list
However, once popovers became a reality, I worked out methods using selection portals inside a popover (sometimes inside a slide control inside a popover), that, for the most part, make up for these deficiencies. You can find working examples of these approaches in the #2 adventure file.