Hi Chip, Thanks for chiming in. I totally agree that named selections shouldn’t be used where sets can be used. I was only considering named selections in places where the current selection would normally be used. Intuitively I thought that moving a named selection into the current selection to work on it (sort, new query, add records, etc.) and then back into the named selection would be costly, but it turns out that it has almost zero cost when used in the specific way mentioned.
Thanks. -- Cannon Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <[email protected]> <www.synergyfarmsolutions.com> > On Sep 14, 2016, at 8:00 AM, Chip Scheide <[email protected]> wrote: > > I think you can see my point - > Yes Named selections have many uses, but I do not see them as a > replacement for sets when working with displayed lists of records where > users can/are adding removing records from the display/table > ********************************************************************** 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] **********************************************************************
