This can happen for a few reasons, but most commonly if the number of variables isn't specified via the v parameter. But if you can attach your que file and html file (zipped if possible) I could take a look and see if something else is going on.
This can happen for a few reasons, but most commonly if the number of variables isn't specified via the v parameter. But if you can attach your que file and html file (zipped if possible) I could take a look and see if something else is going on.
One other thing to check--if you are capturing multiple variables in your custom item--don't forget to put an underscore between the variable name in your que file and the numeric ID of the variable (see attached for an example where the underscores are missing). E.g., if your variable is called "ques1" and gathers 4 variables, be sure they are referred to in your HTML form as ques1_01, ques1_02, etc. as opposed to ques101, ques102 etc. Just one other possibility that came to mind--please let me know if it helps!
Last edited by jarvis24; 10-06-2011 at 10:49 PM.
I'm trying to use the "dummy variable" method. Our researcher does not like the idea of underscores in the variable names and I find it easier to code them directly in HTML than to piecemeal it together with Medialab.
I'm structuring the form based off of the Sample 5 - custom items, dummy variables example. I'm attaching my files, there's a lot of css code included but it should not effect the data being passed, or at least it doesn't in other similar situations.
In my attached file, there are two questionnaires, amp-02 and amp-03. The first one, amp-02, passes the correct data. The second one, amp-03, passes "99" as data. As far as I can tell, they are set up the same way.
Thanks for taking a look.