Thanks for getting back to me Juan,
I upgraded to the latest build of 3.1.1 and this error appears to have been fixed. Something when wrong during the previous upgrade which generated a number of weird errors.
Fingers crossed that all is good now
Heli