# Relation or Array or ? Glide design question **URL:** https://community.glideapps.com/t/relation-or-array-or-glide-design-question/51199 **Category:** Ask for Help **Created:** [October 8, 2022, 1:08am UTC](https://community.glideapps.com/t/relation-or-array-or-glide-design-question/51199 "2022-10-08T01:08:38Z") **Posts on this page:** 1 **Showing post:** 7
### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy) #### Post date: [October 9, 2022, 4:05am UTC](https://community.glideapps.com/t/relation-or-array-or-glide-design-question/51199/7 "2022-10-09T04:05:55Z")
I’d imagine that you’ll probably need to use some variation of the Trebuchet method. It shouldn’t really matter where (which tables) the Account options come from. As long as they can be presented in some sort of list that you can configure an action on, that’s all you need. > [@dizzy The Trebuchet Method](https://community.glideapps.com/t/the-trebuchet-method/48325): > > In certain situations, a single column has the potential to replace an entire table of data. The Trebuchet Method allows you to create an inline array that allows you to create a SIMPLE one-to-many relationship between two sets of data without the need of a log or submissions table. Examples: Who owns which item Who has registered for an event Who has completed which task Pros: no app bloat no additional rows of data fairly easy to set up Cons: Can only track one data point (eg. who has w… --- _[View the full topic](https://community.glideapps.com/t/relation-or-array-or-glide-design-question/51199)._