@Gail Badner, I think the bug has been introduced with 5.2. Therefore I set "worked in" version to 5.1.5 when I created this issue.