Hi, Carl,
if your module contains too many question and test objects, then there could be the issue with SCORM 1.2 4kB limit on cmi.suspend_data field. Each question saves a chunk of data in this field upon completion, so if there's too many questions, you may exceed this limit. If LMS will cut this field, then there will be such error upon recurring entries - g_oSCO is global object, whose structure will be broken if there's no full data in LMS response.
It's hard to say how many question is "too many", because it depends on question types, question sizes etc. 30-40 usual (for example 3-5 choices per question) should fit.
BTW there is no such limitation in SCORM 2004 (i.e. this field has 64kB limit).
Hi, Carl,
if your module contains too many question and test objects, then there could be the issue with SCORM 1.2 4kB limit on cmi.suspend_data field. Each question saves a chunk of data in this field upon completion, so if there's too many questions, you may exceed this limit. If LMS will cut this field, then there will be such error upon recurring entries - g_oSCO is global object, whose structure will be broken if there's no full data in LMS response.
It's hard to say how many question is "too many", because it depends on question types, question sizes etc. 30-40 usual (for example 3-5 choices per question) should fit.
BTW there is no such limitation in SCORM 2004 (i.e. this field has 64kB limit).