We haven't had this problem yet (all of our big courses using WeBWorK
have been in a single WeBWorK course), but will starting this semester
(when we start having big courses for which the sections have to be
defined as separate WeBWorK courses).
I might be wrong, but I suspect that there is no easy way to deal
with the problem. Without having thought about it too much, I expect
I'll end up writing a perl script to manually move the records from one
table to another in the database.
But it would be great if there were a better (already determined) solution.
<| Post or View Comments |>