8 Replies Latest reply on Jul 3, 2017 8:36 AM by smith7180

    Width of "Globals" table


      Like many of you, I have a 'globals' table where I store most of my global fields (radio selectors, layout stuff, etc...).  As my solution has grown, I've put more and more fields (all of them with global storage) into this table, and now I'm curious about the general rule to keep your tables no wider than needed for performance reasons. 


      Am I incorrect assuming this is not an issue with a single record table dedicated to globals?  Will I see any performance improvements if I split a 500 field global table into 5 100 field global tables?