Written by tringate the 21 May 10 at 01:27.

Add the function of full display of the question text when hovering over a question in the dropdown question display box.

Add the function of full display of the question text when hovering over a question in the dropdown question display box.

Written by tringate the 21 May 10 at 01:23.

To be able to identify these incomplete surveys and delete them easily, add a button to the survey tool bar to display incomplete but not saved surveys.

To be able to identify these incomplete surveys and delete them easily, add a button to the survey tool bar to display incomplete but not saved surveys.

Written by tringate the 21 May 10 at 01:12.

By adding a button to the sub question screen to "Make Label Set" a survey author could save time and avoid having to enter in the same information again just to make a label set template.

This would let an author make label sets from existing questions with no additional data entry.

Making Label Sets a easy to maintain library of sub questions.

By adding a button to the sub question screen to "Make Label Set" a survey author could save time and avoid having to enter in the same information again just to make a label set template. This would let an author make label sets from existing questions with no additional data entry. Making Label Sets a easy to maintain library of sub questions.

Written by tringate the 21 May 10 at 01:03.

Add a button/function to the label set to do a "global update" to all questions in non active surveys that have used that label set.

Add a button/function to the label set to do a "global update" to all questions in non active surveys that have used that label set.

Written by tringate the 20 May 10 at 14:53.

Add a column in the survey list screen to give estimated survey table size.

The database type is known, and the estimated table sizes limits are known. A survey could be scanned and an estimated table size shown and those nearing the limits could be displayed in a different color.

Here is what the manual says about table size and unfortunatly after writting a very long survey and then trying to activate it I discovered I was way over the limit of what my database would accept.

...regarding survey size
Note: 'Survey size' refers to the maximmum number of questions (and answers) in your survey - don't confuse this with the number of replies on your survey (there is no limitation on that). Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table.


•MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB.
•MySQL InnoDB: Maximum number of 1000 columns

Add a column in the survey list screen to give estimated survey table size. The database type is known, and the estimated table sizes limits are known. A survey could be scanned and an estimated table size shown and those nearing the limits could be displayed in a different color. Here is what the manual says about table size and unfortunatly after writting a very long survey and then trying to activate it I discovered I was way over the limit of what my database would accept. ...regarding survey size Note: 'Survey size' refers to the maximmum number of questions (and answers) in your survey - don't confuse this with the number of replies on your survey (there is no limitation on that). Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table. •MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB. •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. The mySQL ISAM engine is the most tricky one. As it allows only up to 65,535 bytes per row and utf8 characters can require up to three bytes per character the maximum may be only 21,844 characters (but this depends on your DB encoding). You can roughly calculate the size of your survey like this: •Every multiple numerical question: 20 chars for each answer •Every multiple choice & array question answers: 5 chars for each answer •Every other question type: 5 chars •Add 10% for the usual overhead