Hi Nick, Dan, David,
I had a short look this morning but then had some work to do
Besides, last week I had a severe computer crash and I still am installing software on my new i7 win7. Which means I don't have software at the moment to test things.

Sure lms.js is the file to go. Take notice that the package you make is unique and may give trouble in other LMSses.

Some wild guesses:
- it seems the data is stored on leaving each page and restored on entering the next page. See line 795 - 796. How about not restoring the data but setting g_sLmsCmiSuspendData tot an empty string?
I would do some experiments with a javascript alert to have a look what is restored and what is stored.

I would also check if your lms doesn't use AICC parameters, I know at least one does. It seems in function, AICC_PrepareData, all data is gathered before sending it. The way the function is build it seems quite easy to skip parts of the data.

Last, in courselab.js in the function LMSSaveState (line 4719) the suspend data, contents of g_oSCO.xml, is copied into variable g_sLmsCmiSuspendData. Maybe this is a suitable place to skip parts of the suspend data. I'm curious what results an alert(g_sLmsCmiSuspendData); would give.

I would like to test myself but the admin tool of the mysql server has changed and I haven't find out how use the new one.