Hey there!

I have a little problem.

During construction of my survey I've created "Numerical input " question which I used to find out the age of participants (i know there is a dedicated question type for that, but I just didn't like the look of it).

Now, I've stopped gathering of the data and I noticed something I did not expected.

The "age" question was set to MIN=16, MAX=60. Yet, in my data, I have people with higher age.



Is it something I've done wrong or is it a bug?

Thx!

PavolDerer wrote: Hey there!
…

Is it something I've done wrong or is it a bug?

…

Since we don't know your LimeSUrvey version and build number : we can not answer if it's a
- potential existing bug
- existing bug fixed
- something with your setup

Please start by LS version number …
(else : i never have such issue personnaly since some year …)

Also: can you add an example survey file LSS with only that specific question, so we can test or check if your setting was wrong?

Hi,

thank you for your feedback.

My limesurvey version is 3.15.9.

My exported question is in attachments.

Thank you!

Please always attach a sample .lss (survey) file, not a .lsq (question) file. It will save the volunteers who are trying to help from having to create surveys.

Thank you for the information, yet I do not feel like getting whole survey design out (given the -experimental, psychological- nature of my survey).

I hope it is understandable.

As Holch requests, all we need is a sample survey with the relevant question(s).

Oh, now I understand. Sorry.

Survey file in attachments.

Thank you.

Hi,
we ask for a *.lss sample to avoid this

If you only send a question it is language dependent.

We only asked for this question.

Also: can you add an example survey file LSS with only that specific question

So you should be able to copy your survey and delete everything not needed.

Best regards
Joffm

Imported your lss : no issue on last git version.
Even without JS : test id done on server, not on client.

Maybe someone deactivate min/max and activate after (this can happen by error before github.com/LimeSurvey/LimeSurvey/commit/...b89f5ef3b9082b4aa2b8 ) , see issue bugs.limesurvey.org/view.php?id=14563 .