Give your Filter Field global storage. Then set up a scripted find performed by a script trigger on the filter field patterned after these examples: Scripted Find Examples
Use a portal to display your list and set up your filter field as a match field in the portal relationship.
Hi, I tried to do it like that, but is not working... I have a problem with the:
Set Field [YourTable::YourField ; Globals::gField]
When I write Set Field, I can't find a way to have those fields in there... I con only write:
Set Field [YourTable::YourField] ......or...... Set Field [Globals::gField]
Sorry if this is very basic, but I couldn't find a way to have both in the same script.
It's a pretty common issue.
When Setting up Set Field, there are two Specify buttons that must be clicked. To get Set Field [Table::Field ; Expression], add set field to your script and click the first button (specify target field). Select Table::Field from the list of fields. Do not click the specify button next to the repetition box. Click OK to close this dialog box. Now click the lower specify button (calculated result) and create the expression to the right of the semicolon (;). Do not try to type in the semicolon.
GREAT!!!!! Thanks!!!! I'm really happy :) :)
Just one more thing... is there an option in which, in the same value list field could be a value that when chosen shows all the records?
- Show all
I call those "special value" value lists where you add a value to the list that is used to perform a different task than when one of the other values is selected.
A scripted find can check the value of the field such as:
If [YourglobalFieldHere = "Show all" ]
Show All Records
put the find script that you have now here
and this can be done even if you are using a "use values from field" type value list. Examples of that can be found in:
This is a free download with many different examples of what you can do when a simple value list isn't enough to get the job done.
Thank you very much for your help! it works perfectly!!!