# Save and update 2 table **URL:** \ **Category:** Ask for Help\ **Created:** [February 7, 2024, 11:59am UTC](https://community.glideapps.com/t/save-and-update-2-table/70577 "2024-02-07T11:59:31Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [February 7, 2024, 12:42pm UTC](https://community.glideapps.com/t/save-and-update-2-table/70577/4 "2024-02-07T12:42:59Z")
Ah sorry, I misunderstood. So in that case you should be able to get what you want using an onSubmit action action with the form. It’s a little but tricky, because when the form is submitted the screen switches context to the table where the row is being added to, so you won’t have direct access to the source table. However, there are ways around this. Have a watch of the below video - I think it might help you with this. > [@sparkle Understanding (and hacking) Form Screens](https://community.glideapps.com/t/understanding-and-hacking-form-screens/69309): > > wave Hey fellow Gliders! Form screens (or form containers) in Glide are critical when creating apps that allow users to add new data (projects, tasks, posts, etc.) to your database. Navigating form screens requires some understanding of screen and table relationships and involves some mental juggling when configuring visibility conditions within the form. In this video, I peel back the layers of a form screen to show you how they work and how to work around a couple of the commonly frustratin… --- _[View the full topic](https://community.glideapps.com/t/save-and-update-2-table/70577)._