> I have now installed a new version - 2013.07.31 - of the code that should fix your problem this time. Thank you for your promptness, Ross. Now the error no longer occurs.