Don, we managed to work this out - the error is related to us reaching the maximum record size limit on the database 65,325 - which we had not appreciated existed. We have now moved records off the database and the problem is resolved.

Thanks

Gordon