General project information
The issue – When trying to view the details in our LMS the following error appears.
ADODB.Recordset error '800a0e78'
Operation is not allowed when the object is closed.
/reports/reportViewer.asp, line 1724
Note: I beleive "TCBYOTheft" is the interaction ID of the first (randomized) question slide.
Any help would be appreciated.
That's a database error...or is that obvious?
Looks like it expects an integer (number) for that record...and you have text in it...and it can't handle that.
Interaction IDs should be integers.
You broke it
You should be able to set other interaction properties, like 'description' with textual content for such purposes.
The Interaction ID doesn't necessarily have to be an integer. It just needs to be unique across the entire course. I've never seen an LMS that demanded an integer for this ID. I think your error might be due to the LMS encountering two interactions with the same ID.
Captivate will track and ensure that the Interaction IDs are unique for all scored interactions in a given project file. But it obviously can't know about the interactions that might exist in another project file that you might happen to bundle up with this one as part of a multi-SCORM packaged course. A randomly-generated integer is a good start, but for even greater insurance of uniqueness across larger multi-module courses, you need to go further.
The problem is that many authors use Captivate templates as a way to initialise course modules and if (like me) you have the quiz questions already set up ready to go in these templates so that you save formatting time, then the Interaction IDs are already allocated in the template, and will be inherited by the projects spawned from these templates. This can mean that more than one module in the course could potentially have an interaction with the same ID.
To get around this, Captivate provides a Quiz Setting for an Interaction ID Prefix so that you can tag all interactions in a project file as belonging to the same module.
So, if you KNOW that your project file will be part of a larger multi-module course, you can make sure each module's interactions are still unique by appending the prefix.
It's always a good idea once you've created your modules to go to Project > Advanced Interaction dialog and just make sure that all scored Interactions have the prefix.
Sounds pretty certain, so I defer!
And running through my scorm docs, you're right, the ID does not have to be a number (I was thinking of the array count, but that's generally automatic, so doesn't apply).
From reading the DB error, it looked like it was erroring on a conversion of the varchar to an integer...and why it would try to do that, unless required, I don't know...but maybe I'm reading the error incorrectly.
At any rate, I've also not encountered this error in regards to repeated IDs between lessons. I believe a DB should store the interaction responses specific to each lesson and the IDs may well be the same for, say, question 1 in lesson A and question 1 in lesson B without any issues.
BUT if you've encountered this, then can't hurt for the IP to ensure uniqueness across all lessons.
I would be curious, however, to know if the OP changes the ID to a numerical value and if that fixes the issue...then is that because changing it eliminated the repeated ID or because the LMS needs a numerical value here
Thank you both for your support.
I have created a very basic short quiz for testing and can safely say, I have no duplicate ID’s and the error still occurred. I’ve tried with and without a prefix/numeric and text, all produce the same error as long as the ID contains text.
I could be wrong however; I really thought I had this working (with text) months ago. Can’t help but wonder something with the LMS has changed. Either way, for now I’ve created a numeric code to enable me to identify the questions fairly easily.
OK. Then the next thing to check is whether or not you have any punctuation marks in your ID strings or in any of the other SCORM setting fields. Captivate and LMSs often have trouble with punctuation in fields, especially when some of those punctuation characters happen to be used in programming code.
Can you check that and get back to us?