Sorry for the newbie question. Is there a guide for that ?

Or maybe I can simply change some settings directly the DB.

As Tpartner says, export the data you collected so far, to be safe (ideally in the format you will want it later for analysis). This is just to make sure if something goes wrong, you still have the data you collected so far. Merging two data files later is relatively simple.

Then you can deactivate the survey, change your settings and then reactivate your survey. Usually, you should be asked if you want to import the old data again.

But I you most probably won't have the date for those that have answered up to this day. Only from now onwards.

Thanks. If I understand the export options, the LSA format is the best suited for that.

No, export the data not the survey.

LSA exports both, the survey structure plus the answers. It is good to have this as backup, just in case.

However, you should also export the data as CSV for example. In the rare case that you are not able to "un-archive" the date when reactivating the survey, you have the survey data as CSV up to the moment of the deactivation.

Later you just export the rest and bring the data sets together into one. Easy peasy.

Thanks. I was able to deactivate the survey, change the setting, reactivate the survey and import results.

The only glitch is that the response IDs are not conserved (the new ones are follows the old ones).

The only glitch is that the response IDs are not conserved (the new ones are follows the old ones).

I don't understand this part. What do you mean with the new ones follow the old ones? For me this sounds about right, that the new responses that you collect after the reactivation start after the ones that you re-imported. Or did I understand you wrong?

Before the deactivation, there was 36 responses whose IDs range fro m1 to 36. After re-import the IDs of the imported responses range from 37 to 72 (there is no new responses for now).

Just to be complete: I did not reimported the responses from the CSV file; I used the builtin functionality to "re-use" the archived response table.

Yes,

This is the issue with get from old table … i prefer to use VV for this issue.

OK. Not a great problem but I will keep it in mind for the next time.

Before the deactivation, there was 36 responses whose IDs range fro m1 to 36. After re-import the IDs of the imported responses range from 37 to 72 (there is no new responses for now).

OK, now I understand. I don't think it is a big deal, but yes, it would be nicer if they would come back with their original IDs, if you use the ID for example to identify them.