-
1. Re: Looping through Found Sets
I agree that a loop makes sense. (And you could have used Post a New Answer to continue this discussion in your original thread).
But it will depend on what criteria you have to use for your finds and how you make it available to your script.
You might, for example, assign criteria to a variable as a list: Set Variable [$Fruit ; value: List ( "Apple" ; "Pear" ; "Kiwi" ; "Grape" ) ]
You can then use the get value function to extract one value at a time from the variable inside your list to specify one of these values as find criteria.
For examples of scripted finds that could be adapted to this type of loop, you might examine this one:
-
2. Re: Looping through Found Sets
Wasn't sure about protocol - new post or Post New Answer .. thanks for info.
Re your most recent suggestion, are you suggesting I create two variables (Category - with 8 items) and (sub-category with 6 items) and script in such a way that it performs 48 finds with the other scripted actions between each?
I'd want the scripted Finds based on both variables - stepping through all 6 possible combinations of Category 1, first, then all 6 combinations of Category 2, etc.
Using example from link included in your post, I think my situation would require a nested loop in order to go through all 6 possible combinations of Category 1 before advancing to Category 2 and so on. Do you agree? Hate to ask but can you illustrate how a nested loop (if that's the right idea) would work in the example below?
Set Variable [$FruitList ; value: Globals::gFruitList ]
Enter Find Mode []
Loop
Set Variable [$K ; Value: $K + 1 ]
Set Field [YourTable::Fruit ; GetValue ( $FruitList ; $K) ]
Exit Loop If [ $K > valueCount ( $FruitList ) ]
New Record/Request
End Loop
Set Error Capture [on]
Perform Find[] -
3. Re: Looping through Found Sets
While many of the examples use a global field, you probably do not need one in your case. The global fields in those examples are used as a way for a user to manually select/enter search criteria while in Browse Mode that a script can then access while in Find Mode in order to set up search criteria.
In your case, there's no user inputting the search criteria so you don't need the global field. That's why my example used a calculation with a list function instead of a global field reference.
Set Variable [$FruitList ; value: List ( "Apple" ; "Strawberry" ; "Grape" ; "Peach" ) ]
Set Variable [$Sources ; value: List ( "Imported" ; "Local" )
Set Error Capture [on]
Loop
Set Variable [$J ; $J + 1 ]
Exit Loop If [ $J > ValueCount ( $Sources ) ]
Set Variable [$K ; value ; 0 ]
Loop
Set Variable [$K ; Value: $K + 1 ]
Exit Loop If [ $K > valueCount ( $FruitList ) ]
Enter Find Mode []
Set Field [YourTable::Fruit ; GetValue ( $FruitList ; $K) ]
Set Field [YOurTable::Source ; GetValue ( $Sources ; $J ) ]
Perform Find[]Put code here to process the found set produced by this find.
End Loop
End Loop
-