Virtual Value List helps developers build transient value lists based on the contents of global variables. By basing value lists on global variables, developers can be spared most of the schema overhead associated with other techniques for value lists with programmatically specified values.
This module is based on value list demos by John Ahn and Andries Heylen, and a technique by Marcelo Piñeyro for coercing value list ordering. Joel Shapiro discovered and reported significant bugs in earlier versions of this module.
You must use a copy of FileMaker Pro Advanced to install the custom functions for this module.
- Import all the custom functions to your solution file.
- Copy or reproduce the VirtualValueList table into your file.
- Reproduce the relationship between the VirtualValueList and VirtualValueList__related table occurrences in your file.
- Import the "Virtual Value List" module script folder into your file.
- Edit the "Go to Virtual Value List Layout" script to go to a layout in your file based on the VirtualValueList table occurrence.
- Add the "Enforce Virtual Value List Record Requirement" script as a sub-script of your file's startup (OnFirstWindowOpen) script.
- For each value list you anticipate using simultaneously in your solution, mimick one of the value lists from this file. Choose which value list to mimick based on whether you need that value list to set a hidden ID value or not.
You will need to create new fields in the VirtualValueList table for each virtual value list you create.
For each value list you create, FileMaker will warn you that value lists on unindexed fields don't work. Don't worry; these value lists work if they are set-up correctly.
See the demos in this repository for examples of how to set-up virtual value lists in your solutions.
To use Virtual Value List with pop-up menus and drop-down lists:
- Select one of the virtual value lists to associate with the pop-up menu or drop-down list.
- Add to the field an OnObjectEnter script trigger calling the "Exit Script OnTrigger with Parameter as Result".
- In the script parameter to the OnObjectEnter script trigger, use the VirtualValueListSet custom function to set the virtual value list values to use with the field. If you're using ExecuteSQL to get the values to set, the VirtualValueListSliceAndSet function may be worth considering instead of the VirtualValueListSet function.
- As a best practice, add to the field an OnObjectExit script trigger calling the "Exit Script OnTrigger with Parameter as Result" script.
- In the script parameter to the OnObjectExit script trigger, use the VirtualValueListClear custom function to clear the virtual value list. This cleans-up the global variables used to drive the virtual value list, which is no longer needed when the field is exited.
To use Virtual Value List with radio button and checkbox sets:
- Select one of the virtual value lists to associate with each radio button or checkbox set.
- Use an OnLayoutEnter or OnModeEnter script trigger to set each virtual value list via the VirtualValueListSet custom function. If you're using ExecuteSQL to get the values to set, the VirtualValueListSliceAndSet function may be worth considering instead of the VirtualValueListSet function.
- As a best practice, consider using the VirtualValueListClear function with an OnLayoutExit script trigger to clear a virtual value list when leaving a layout using the value list.
You can set up as many Virtual Value Lists in your solution files as you want. Use the virtualValueListID parameter of the custom functions to address different value lists. The numbering scheme to use with virtualValueListIDs is up to you, and you can make it whatever you want. This does not have to be FileMaker's internal ID for the value list (but that's not a bad idea!).
For value lists with hidden ID values to work correctly, the VirtualValueList table must have at least as many records as the largest such value list. Edit the "Get Virtual Value List Settings" script to set the number of VirtualValueList records to use with your solution.
Anyone may do anything with this software. There is no warranty.