# I have built an attendance app but it takes up too many rows

**URL:** <https://community.glideapps.com/t/i-have-built-an-attendance-app-but-it-takes-up-too-many-rows/60114>\
**Category:** Ask for Help\
**Created:** [April 4, 2023, 6:34am UTC](https://community.glideapps.com/t/i-have-built-an-attendance-app-but-it-takes-up-too-many-rows/60114 "2023-04-04T06:34:51Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [April 5, 2023, 3:07pm UTC](https://community.glideapps.com/t/i-have-built-an-attendance-app-but-it-takes-up-too-many-rows/60114/15 "2023-04-05T15:07:21Z")

</div>

Hola!

I think this thread can be useful for you [Glide Big Tables - pricing - #7 by gvalero](https://community.glideapps.com/t/glide-big-tables-pricing/58578/7)

There are still other options to improve your table structure, but you have to evaluate and discard one by one, such as using an array to store the data (it’s ok to save data, but kind of hard when you need to parse and retrieve specific data).

Saludos!

---

_[View the full topic](https://community.glideapps.com/t/i-have-built-an-attendance-app-but-it-takes-up-too-many-rows/60114)._