For now your structure is less complicated - I'll go into that more later.
You have the right idea. What I would recommend is to separate the Inspection level details from the Questions. So your "result" table becomes 2 tables -- "Room Inspections" and "Inspection Results".
Room Inspections - ID, Operator Name, Date, Floor, Room Number
Inspection Results - ID, Room Inspection, Question, Answer, Note
For inspection entry, there are many ways to implement the inspection entry depending on YOUR prefered process.
Assuming that the "Operator" is entering the Room info AND Inspecting at the same time, I would Add a Room Inspection row and when Save is tapped, attach actions to the Form Save that will:
- Copy the Questions into the Inspection Results table for THIS Room Inspection
- Navigate to a Table View that is in QuickEdit mode. This view shows the List of ALL questions with the ability to answer each question AND enter a Note.
If you wish for Room Inspections to be entered previously and an Operator then SELECTS a Room Inspection to perform. I would in this case, have an "Inspect" button somewhere - maybe show Room Inspections in a Deck View with this button. When the "Inspect" button is tapped, it performs the actions noted above - 1) and 2),
Circling back to the structure...
I know it seems that you only need a static list of questions now. But you will likely find in time that you DO need different set of questions for different types of rooms/situations.
For example, if a room has two beds versus a single bed, you may may want questions tailored to those specific rooms. Or if a room is a suite with kitchenette versus a studio, Or if a room is Pet friendly versus one that is not. This is where the Template approach will be extremely useful. You can create a Template for each type of room.
Not only can you tailor the questions to each room, but you can modify the list of questions to each room type independent of the others.
I hope this helps!
LinkedIn
Twitter
