Thanks for the reply Adam.  I'm already using v5.3 though.  I don't know if this was an issue in the previous release.  Are you able to reproduce this problem?