Designing a prefs system: It would be easiest to use a table, with the load & save functions already in place, either as key pairs, or as a single row, with columns for each pref. Questions: What is the overhead (memory space/access time) of a table, compared to using an array? Is that overhead different for, say, 2 columns by 10 rows compared to 10 columns with 1 data row? Given that there is a table.dispose method, is there a runtime table.create so that the load/save routines could be used to deal with an array of prefs (if that is lower in persistent runtime overhead)? Maybe someone's done this before - I can't see an obvious example in the fora or example files.