This looks nice, Kevin! Would you be able to cite some examples where this might be the preferred approach over using something like a dynamic filtered value list or maybe even Magic Value List?
It’s another way to skin the proverbial cat… found-set aware… doesn’t require value lists or relationships… the results can be sorted in ascending or descending order.
Kevin – Great concept and solution. Learned a lot and it has the squirrels running.
I had a problem with the script when adding the process to my database: it only displayed the data from the first column chosen. Turns out the dev::zz_g_pseudo_index field needed to be on the calling layout. I didn’t see this mentioned in your description. If you have a better solution, please share it.
In my experience dev::zz_g_pseudo_index does not need to be on the calling layout; unless I’m mistaken, my demo works fine without that field being on the calling layout.
This looks nice, Kevin! Would you be able to cite some examples where this might be the preferred approach over using something like a dynamic filtered value list or maybe even Magic Value List?
It’s another way to skin the proverbial cat… found-set aware… doesn’t require value lists or relationships… the results can be sorted in ascending or descending order.
What a shock!
A mac screenshot here! ;)
There have been quite a few of them over the last year or two.
But a Fabrice sighting is a much rarer occurrence. Nice to see you my friend.
This fits in nicely with the “Windowing in FM 16” article, as well!
https://filemakerhacks.com/2017/05/09/windowing-in-fm-16-first-impressions/
I like the “found-set aware… doesn’t require value lists or relationships” for this technique!
Thanks, KF
I appreciate the kind words Beverly!
Kevin – Great concept and solution. Learned a lot and it has the squirrels running.
I had a problem with the script when adding the process to my database: it only displayed the data from the first column chosen. Turns out the dev::zz_g_pseudo_index field needed to be on the calling layout. I didn’t see this mentioned in your description. If you have a better solution, please share it.
Hi Larry,
In my experience dev::zz_g_pseudo_index does not need to be on the calling layout; unless I’m mistaken, my demo works fine without that field being on the calling layout.
Regards,
Kevin
Thanks Kevin. I’m sure placing the field on the calling layout solved my issue. I will dig a bit deeper.