Jody, I have the same setup using a single configurable list view. But the reason I want to use an array based listbox with formula columns is because I want to display large selections of rows where none of the data is in a 4D record (e.g. a SQL cursor). To make this work, you have to create a "dummy" table in 4D to create a selection of records. And then you have to use named selections if you need more than one display in the same process. And tables can't be used in components. It would be greatly simplified if the number of rows was simply managed by the single boolean array listbox.
John DeSoi, Ph.D. > On Aug 31, 2016, at 3:30 PM, Jody Bevan <[email protected]> wrote: > > Since v12 of 4D we had one form for all outputs. It used a listbox. We let > users determine which column they would show or not. We also let the system > administrator add new columns that were based on fields or formulas that they > could make up. > > When a user selected one of the formula based columns it worked just fine. It > was slower than without it, but if one needs the information it saves time > overall. ********************************************************************** 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] **********************************************************************
