@RandyHayes Honestly, I don't know if I need a form control lol. This is my first app so I'm learning as I go. From my standpoint it seemed the simplest--albeit maybe not the most efficient way to get the functionality I need.
I think I understand the concept behind @KrishnaV 's approach, but I don't know how to implement it.
For clarity, let me explain what I need to do and maybe that will help with solutions.
The app is wired up to a SQL db storing employee data. All the tables are normalized. The purpose of the app is to view historical records by employee as well as add new records.
A user opens the app and selects an an employee from a list on the previous screen which also displays their most recent records.
They need to add some new records so they click a button that takes them to the screen we are discussing.
I'm trying to build some way for the user to independently add records for the selected employee. (There are approximately a dozen individual tables related to the employee table.)
The user needs to be able to add records to all the tables, or some of the tables via this screen and submit them all with one click in a batch.
I guess the tricky thing about this whole thing is if it was one big form going to a de-normalized table it would be simple. But it's multiple normalized tables that need to be updatable via one screen. Setting up the individual forms in the way I did was my clunky attempt to replicate the functionality of a single form to update all or some of the tables.
