# App with lots of user entered data
**URL:** https://community.glideapps.com/t/app-with-lots-of-user-entered-data/74060
**Category:** Ask for Help
**Created:** [June 12, 2024, 12:07am UTC](https://community.glideapps.com/t/app-with-lots-of-user-entered-data/74060 "2024-06-12T00:07:02Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@AndyV](https://community.glideapps.com/u/AndyV)
#### Post date: [June 12, 2024, 12:07am UTC](https://community.glideapps.com/t/app-with-lots-of-user-entered-data/74060/1 "2024-06-12T00:07:02Z")
I would appreciate anyone that point me in the right direction with the following.
App allows anyone to create an account and a profile.
After creating an account, users are asked to complete 7 surveys.
Each survey has 10 questions.
Users can comeback anytime (1 hour, 2 days, 3 months, etc) and edit their answers to the questions.
That is it.
I assumed I would create 1 table for each servey, but how to how link it to the users ID.
only one row per person
They caan come back and edit later.
Thanks,
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [June 12, 2024, 12:38am UTC](https://community.glideapps.com/t/app-with-lots-of-user-entered-data/74060/2 "2024-06-12T00:38:03Z")
You would need 7 tables to store responses to each survey.
And maybe 7 helper tables where you will construct custom forms.
> [@How do I create a custom form?](https://community.glideapps.com/t/how-do-i-create-a-custom-form/25014):
>
> I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using [User Specific Columns](https://docs.glideapps.com/all/reference/data-editor/user-specific-columns) and [Relations](https://docs.glideapps.com/all/reference/data-editor/computed-columns/relation-column) Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particular…
That way, people can go back and continue filling their form. Add a way for them to view their submitted responses and edit them as well. Prevent them from submitting a new entry should be straightforward with a relation to each response table, and hiding the button to open the form when the relation is not empty.