Your client DB is ?

@DenisChenu, client is using PHP 7.4.3 and mysqlnd 7.4.3

Strange , mysql with such number of columns …

Do you have a db dump too?

lss too maybe

Yeah, we know that problem. The response table is so close to the table field limit, that the length of the field names become relevant.

So if you copy that survey to a very low survey ID , like 2, you will be able to activate it because the field names are much shorter, and thus that internal field limit is not reached.

@c_schmitz, thanks a lot for the very helpful hint!

Do you think this is also causing the export problem? How can we approach this?
Currently they are merging 2-3 file exports but that is painful since they need to analyze data weekly or even more often and new responses pop in every day.

@ollehar I can not provide a full DB dump. There are dozens of surveys and there is a lot of medical data in it so it is too confidential. Sorry!

Response export limit is most likely caused by PHP max_input_vars setting, which defaults to 1000. Try to raise that to 2000.

@c_schmitz, I was able to get the data into our test system by:

1. Adjusting the survey ID at the LSS file to "111".
2. Importing the surveys with the adjusted LSS file which then COULD be activated
3. Exporting data using VV export
4. Importing using VV import

I was also able to export ALL data because we always raise "max_input_vars" to 10.000 at our system.
So that was VERY helpful, thanks a lot.

Maybe you should code a warning if someone tries to expoirt a survey with the number of columns being > max_input_vars!?

I am attaching the new survey 111 as LSA file for further testing.

Maybe you should code a warning if someone tries to expoirt a survey with the number of columns being > max_input_vars!?

I think we already have seom issue reported about max_input_vars , and already add some warnings in Question edition maybe ?

Added a warning to response export if setting is too low in LS5.