Hello Anne,

I confess that I took me quite some time to finally understand what your problem was, but I think I've eventually got it - in hindsight it was obvious.

What isn't working is the "print code set" function for the "Q3 coding" codeset, right?

Assuming I've got it right: I found a quick workaround, which might be suboptimal, but should allow you to continue working. When exploring this (rather big, and organised in a way that looks hard to manage, to my uninformed eyes) codest, I noticed that most codes belonged to the branch that starts with the "Study methodology 306" code. It is quite difficult for me to find out why the "print codeset" option didn't work for this codeset in particular, so I made a guess and hypothesised that perhaps the codes go too deep (in terms of number of levels used) breaking this particular functionality (for reasons that I will need to clarify).

To verify this hypothesis, I've moved the "Study methodology 306" back one level, into the root of the "Q3 coding" set. Tried again and yes! The "print" icon started working again. Please do note that this operation retained all your "coding data", it is just a "cosmetic" change that only affects the position of your codes in the tree, not the work done while coding references.

I hope this solves your immediate problem - please let us know if it doesn't!

For me, it suggests where I should start looking for the root cause - you definitely have found a bug, and it should be fixed. However, I can't promise when I will look and/or solve the problem once and for all - it might be a rather laborious affair and I might struggle to find the time.

Regarding your other questions: there is a maximum level of codes for each codeset type; each code name can be up to 255 characters long; this number is fixed for all codes, does not depend on where a given code appears in the tree.
If the Silverlight version works for you, there is no immediate need to "convert" to the Web version. EPPI-Reviewer v.4 will remain available at least for the whole of 2020 (unless something unforeseen happens to make us change our plans). Hopefully during this time the Web version will mature enough to make it more attractive. Between 2021 and 2022 we expect Microsoft to drop all support for Silverlight, at that point we hope that the Web version will contain all required functionalities and will be more than mature - thus, we are likely to shut down version 4 at that point. Short version: there is still plenty of time.

I hope this helps,

Sergio