Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.
Hm, alternative?
You see, as this is a limitation of MySQL and there is this flat database structure of LimeSurvey you can not do anything on this level.
1st you may revise your questionnaire.
E.g. If there are long arrays(text) or arrays(number) with subquestion relevance you may use micro-tayloring to shorten this.
2nd you may split the survey.
In the end-url of the first survey you link to the second one.
Joffm
Volunteers are not paid.
Not because they are worthless, but because they are priceless
MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB. (about 1570 columns)
MySQL InnoDB: Maximum number of 1000 columns
MS SQL Server 2000: Maximum number of 1024 columns
Postgres: Maximum number of 250-1600 columns depending on column types. The maximum number of columns can be quadrupled by increasing the default block size to 32k. See
Installation FAQ
and
PostgreSQL FAQ
.
Volunteers are not paid.
Not because they are worthless, but because they are priceless
MS SQL Server 2000: Maximum number of 1024 columns
With a war ning about MS SQL …
Sometimes : you can activate survey, all seems good, but for some user : they can not save their data : the reason is «Bytes per row in memory-optimized tables» maximum value is 8,060 for one row (one reponse)
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.