Hi Chip, Correct I believe. Looking at the chart: http://doc.4d.com/4Dv16R4/4D/16-R4/4D-Server-Sets-and- Named-Selections.300-3423889.en.html
not only is the $test set local to the client machine but the <>test set is too - they differ in scope on the client machine's processes. But the 'regular' test set's scope (as I should think of it) is both the client machine and the twinned process on the server. That's probably by design within 4D I'm guessing. I always looked at that chart as specifically referring to triggers but now I know it's accurate for sets and named selections as well. Which is a pretty cool feature I haven't taken much advantage of. On Wed, Dec 6, 2017 at 6:41 AM, Chip Scheide via 4D_Tech < [email protected]> wrote: > clarification please. > > if the set created on the client side is "$Test" then it is NOT > available in the trigger/EOS correct? -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
