Hi TracyFrom what I humble knowledge I have of the issue, this is what I can tell you:When publishing to SCORM, Lectora stores the user's answers in a single variable called "cmi.suspend_data" which in turn is communicated to and saved in the LMS database.When the user accesses the content object again, the contents of cmi.suspend_data is retrieved from the LMS and made available to the content object. Because data is appended to the variable for each question the user answers, Lectora provides the scripting needed in the content object in order to split (or slice) the variable and present the data in the corresponding input fields across the content object.If you are using Saba as LMS, you'll have the possibility of activating the "SCORM API applet debug" mode which shows most of the communication between content object and LMS. Here you'll also be able to have a look at the cmi.suspend_data variable and its contents at different stages.You'll also have this functionality with most SCORM RTE's and test-beds.I hope this explains things a bit.Edited By: berntsen on 38448.3220138889
