For a list of that type, I'd want to be able to auto-complete and that is possible if you use a drop down list. There are ways to keep the user from entering a value that is not a member of a value list. A validation field option can pop up an error if it's not a value in the list or an auto-enter calculation can clear the field when it's not a member of the value list.
I wish that I could post the download link for "Adventures In FileMaking #2" as it is all about various enhanced value selection methods, but I haven't quite finished the file. I have finished "Adventures In FileMaking #1" which demonstrates 8 different forms of conditional value lists so you might want to take a look at it.
I'll take a look! Thanks.
So it sounds like the solution I'm going for is not attainable using a standard value list controlled by the Inspector tool?
Wow, I left out an important bit of information...
I am working in FMP 11 Advanced.
What I was saying was that it looked to me like you were overlooking a key feature that would make some of the other features much less useful. If you can type in a few letters and see the list filter down to just one or a few values automatically, the need for other means to control the value list become much less critical.
PhilModJunk, I just got a chance to go over "Adventures in FileMaking #1."
Lots of great info and examples in there.
But It also made me wonder...
All the examples in that tutorial are conditional value lists, using a combination of table instances, scripts, script triggers, and value lists set up as fields...
Would you recommend, based on the needs I described, that I use those techniques rather than a less complicated "Custom Value" list dictated solely by the Value List's custom values and the Inspector | Data panel?
Know what I mean?
If your value list has more than just a few values (as I assumed was the case for you), I would not use custom values unless I am very, very confident that I won't need to make changes to the values listed in the future. Once you get beyond a 5-10 values, it becomes easier to manage them as records in a table. And a table based source for your values gives you value selection options that go far beyond what you can do with a simple value list (and that's the main topic for AIF #2 that I hope to release soon...)
Got it, that explains it very well.
I'll look forward to AIF #2, and in the mean time start looking into getting my values into a table.