Sorry. I meant that I have a table called ITEMS. And in that is a big list of objects - for an inventory. I have categories for each of these items, and within those I have subcategories etc. I wasn’t sure how to do that. So at the moment inside the table ITEMS, I have a column CATEGORY, then a column CATEGORYSUB, then a column CATEGORYSUBSUB, and a column CATEGORYSUBSUBSUB. And each of those are set to be REFS, sourcing from separate tables - I have a table called CATEGORIES, a table CATEGORYSUBS, a table CATEGORYSUBSUBS and a table CATEGORYSUBSUBSUBS. That’s how I’ve built it, as I wasn’t sure how else to do it. And then inside those tables, they are ref’d to each other. Does that make sense?
For more info: Inside the “CATEGORIES” table, I have columns _RowNumber, CategoryID, CATEGORY, CATEGORY IMAGE, IMPORTANT and Related ITEMSs that last one was autogenerated by AppSheet).
I’m happy to change the way I’ve built it - I’m asking to find out how best to store and use “subcategories” and “subsubcategories” etc for items in the database.
The app I’m making then should have “CATEGORIES” as an option at the bottom, then you see a list of all the main categories. You click one, and it shows the subcategories. You click again and you see the subsubcategories. Then again to see the subsubsub categories. Ideally at each point you’d see all the products that are have no further subcategories. The way a normal inventory app does it, I guess.