When you activate a survey, you can't make change to certain parts of the survey (e.g. add questions, add answer options and subquestions), because this requires changes in the database. So make sure that your survey is READY and FINAL when you activate it. Because once you are in field and see the need to de-activate the survey, all responses up to this point will be archived. So I personally try to avoid to have to de-activate a survey during fieldtime at any cost.
Now, sometimes it is necessary and then I export all responses BEFORE deactivating, just to make sure I have those responses secured. If everything goes wrong, at least the responses are still there and somehow I can join different files with responses later manually in some way.
So as said, when you deactivate the survey, all responses up to this point get archived. You then can do the changes to the survey and when you reactivate, as you can see in your screenshot 2 that you can "reactivate" old participant tables. This usually works fine, but depending on the changes you made, this might not be 100%. So better to avoid this as much as possible.
So whenever you deactivate, the answers so far "disappear" (get archived). You need to remember to restore them when you activate again. During testing, this is no issue, because you won't want to have the test responses mixed with the real responses.
So before you go into field, you can either deactivate and activate the survey to have a clean response table, or you delete the test responses manually from the GUI.
But remember, during the real field time, avoid deactivating if possible. That's why you should test thoroughly BEFORE going into field.
To be honest, seeing the questions you have today, wanting to go into field tomorrow sounds like a stretch and there is / was very little time for testing. Usually, for me, the testing process takes longer than the programming stage.
Help us to help you!
- Provide your LS version and where it is installed (own server, uni/employer, SaaS hosting, etc.).
- Always provide a LSS file (not LSQ or LSG).
Note: I answer at this forum in my spare time, I'm not a LimeSurvey GmbH employee.